Kimi Päivärinta

Date: 30.10.2025 (2025-10-30)


Kimi Päivärinta (30.10.2025) • https://www.linkedin.com/in/kimipaivarinta/ • CTO at Fondion () • ERP for construction companies • Lives in Vienna now

Questions: • Who are their main customers? • They do not have accounting -> income management, proposal calculation, • They are a Service platform -> a lot of integrations - e.g. accounting system • They are mainly focussed on FIN: main market is on 4 accounting tools • Main value: visibility and transparency of their projects • A lot of bankruptcy in construction -> Fondion can give them the ne • growing 300% • Geographic: Finland only; one customer that works in Estonia and Germany as well; looking into Netherlands -> they do not do accounting because of that • Size: 1 to 10 Mio in revenue -> CEO and 5 to 30 employees • CEO is doing a lot • They have a few that have 40 to 50 Mio. • One big value is calculation of projects with live data • They integrate with hardware stores to get latest prices • Do they have agentic features? • Not any customer facing features yet • He wants to focus on really valuable features - not just for the sake of it • One low hanging fruit: • Chatbot to prompt analysis -> challenge the accuracy is limited • People get more and more experienced with LLMs • They had a lot of icons -> people do not understand the icons • He is not really aware of actually valuable features • Legacy software • No problem • Most important integration is accounting system -> they sell a bundle with accounitng -> push customer to replace • Insight from KPMG: Finland is very ahead with APIs etc. (electronic invoices was launched in 2007) • Try to find out how a partnership could work? Integration into their system? • • What are their AI features? • • Biggest challenges? • Kaiko Health: he was running the integration team -> they built integrations to old legacy systems -> security is the big challenge during transfer • If integration via UI have been possible - integration would be so much easier • API only supported part of the data they required • Integration via DB does not validate data (done by the BE / FE) • Problems: • How to get text file to server • Internal automation? • Internal tools: • They use LLMs -> mapping Excel to other Excel • ChatGPT • In development • Crafting newsletter, summarising information etc. (MSFT copilot) • Feedback to my idea? • What about desktop applications? • Who is managing the tool? • His objections: • Application - who sets up the • He will not do any integration on top of RPA -> a lot of maintenance and customer support
• They only do integrations that are used by 20 to 30% of customers • for the rest they have their own API which customers can use -> some customers tasked small dev companies to build the integrations for them • His problem with RPA: • Their API documentation often does not have all relevant endpoints -> a few things to fix • He would happy to use the Rest API part of this -> we could provide support for it - then they would be interested ->we have the risk of maintaining it • Integration to the accounting systems: one new edge case every two weeks with integrations -> there are always some edge cases • 150 customers using integrations