Integration
Connect your product to their accounting system.
Transfer agreed customer, invoice or status data between your product and the customer's accounting system. Access, data mapping and error handling are defined before the build.
For software companies and implementation partners
Deliver the integration your customers are waiting for.
I build integrations and defined workflows for software companies and implementation partners. You keep the customer relationship. I handle the agreed technical delivery.
One defined project. A clear quote. Documented handover.
01Your product
02The integration
03Your customer's system
Examples of what I can build.
Start with the missing piece in a customer delivery.
Workflow
Automate the handoff between systems.
Move information when a job is completed, a document arrives or a status changes. Cases that need review go to a person instead of disappearing between systems.
AI access
Connect an assistant to the data it needs.
Give an AI assistant access to a defined set of system data through an MCP server. Permissions and any allowed actions are agreed before development.
These are examples of possible projects, not a catalogue of ready-made integrations.
You keep the customer relationship.
A customer needs a connection. Your team already has a roadmap. I take on the missing piece as a defined project, rather than taking over the customer relationship.
Your side
You define the customer need, arrange the necessary access and approve the result. Customer pricing and the commercial relationship stay with you.
My side
I scope the technical work, build the agreed flow, test it with you and document the handover. I can join technical customer meetings when useful.
Need the same flow for several customers? We agree on repeat deployments and reuse separately.
I built BilagPilot.
BilagPilot finds accounting entries without supporting documents and brings follow-up into one place. I bring that experience with accounting systems into the work I build for you.
You work directly with me, from the first conversation to the handover.
See BilagPilot
Systems I have worked with
From a customer request to a tested integration.
We start with one flow and agree what counts as finished.
- 01
Clarify
The systems, the data and the result. I check available interfaces and identify dependencies before quoting.
- 02
Build
I implement the agreed flow, with checkpoints for your team along the way.
- 03
Test
We test the agreed cases, including missing data and failed requests. You review the result before it goes live.
- 04
Hand over
Code, setup instructions and responsibility for ongoing operation are documented. Your team knows what has been delivered and how to take it forward.
The quote sets out the schedule, including dependencies on access and third-party approvals.
A clear scope. A fixed price.
You get a quote for a defined delivery, not an open-ended list of development tasks.
- 01
A free first conversation
20 minutes about the request and the systems involved. We establish whether a closer technical review makes sense.
- 02
A clearly scoped quote
What will be built, what is excluded, how it will be tested and the fixed price. Any paid discovery is agreed separately before it starts.
- 03
A defined delivery
Payment milestones are set out in the quote. Changes outside the agreed scope are priced before I build them.
- 04
Optional ongoing support
Hosting, monitoring, support and later improvements can be agreed and priced separately.
Payment terms, usage rights and any ongoing commitment are set out in the quote before you decide.
A good starting point
- A concrete customer need or repeated request.
- Known systems and someone who can arrange access.
- A budget owner and someone who can test the result.
Needs narrowing first
- The brief is to automate everything at once.
- No one owns the project or can approve the result.
- The necessary access is not yet available.
We can use the first conversation to identify a smaller first delivery.
Frequently asked questions
01Can you work under our brand?
Yes. I can work as your technical subcontractor. We agree on branding, customer contact and responsibilities before the project starts.
02Can you work with our systems?
I check the APIs, available data and access requirements before committing to the build. The systems shown on this page describe my experience, not a catalogue of ready-made connectors.
03Does the project have to use AI?
No. A regular integration may be all the job needs. AI is included only where it has a defined purpose, with permissions and review requirements agreed for that step.
04Can our team take over later?
Yes. The agreed code, setup and access are documented so another developer can take over. Ownership and licensing of project-specific code, reusable components and third-party software are agreed before we start.
05What happens after delivery?
We agree who runs the integration and handles issues. Ongoing support is scoped and priced separately, with support hours and response times stated in the agreement.
06What data will the integration access?
Only what the agreed flow needs. Permissions, logging and data handling are defined before customer data is connected. A data-processing agreement is put in place where required.
Bring the integration your customer is missing.
Tell me which systems need to connect and what should happen between them. We will look at what is feasible and the next step.
Discuss one integration20 minutes with Kevin. Free, with no obligation.An honest no if the project is not a good fit.Prefer email? Describe the request in a few lines.Please do not include passwords, API keys or live customer data.