It looks like you’re from {country}
CRM
A quote gets accepted online through Teamleader on a Friday afternoon. Nobody is looking at Teamleader on a Friday afternoon, so the project it was meant to kick off starts the following Wednesday instead, when someone happens to open the app and notices the status changed.
This is the specific trap of a tool that does more than one job. Teamleader is CRM, quoting and invoicing in one place, which is genuinely convenient — until the convenience means three different teams each assume somebody else is watching it.
Teamleader Focus — the rebrand of what used to be Teamleader CRM plus Invoicing — is Belgian software combining CRM, quoting, invoicing, time tracking and light project management in a single product, aimed squarely at SME service businesses and agencies. It is genuinely popular in the Benelux, in the same market segment as the smaller accounting packages elsewhere in this bank.
That breadth is also the thing to plan around: because Teamleader can invoice on its own, a business also running Exact Online or Moneybird has to decide explicitly which system actually sends the invoice, rather than discovering it does both and the numbers between them disagree.
Its API — Focus, a documented REST API with OAuth 2.0 — covers Companies, Contacts, Deals, Quotations and Invoices as first-class objects, along with webhooks on most of them, which makes "a quote was accepted" or "a deal moved stage" something a website can react to immediately rather than something a person has to notice.
Two of these come specifically from Teamleader doing several jobs at once, which is exactly the thing that makes it appealing in the first place.
A customer accepts a quote online. In Teamleader that is a status change; on the ground it should mean a project kicks off, a delivery date gets planned, a welcome email goes out. None of that happens until somebody notices the status by hand.
What you see instead
A webhook on the quote-accepted event starts the next step immediately — a project created, a notification sent to whoever delivers the work — the same minute the customer clicked accept.
A business running Teamleader for CRM and quoting, and Exact Online or Moneybird for the actual books, sometimes ends up invoicing from both — a project manager sends one from Teamleader because it is convenient, finance sends another from the accounting package because that is the process. The customer gets two invoices for one job.
What you see instead
One system is named the invoicing system of record, and the other only ever produces the quote or the deal that feeds it — never a second invoice for the same job.
A web form and a manually entered deal spell a company's name differently, and Teamleader creates two Companies instead of recognising one. A quote history and an invoice history end up split across records that should be the same customer.
What you see instead
New Companies are matched on VAT or KVK number where it is available, rather than a free-text name, before anything new is created.
This one is less about hours than about delay compounding. If quotes are accepted online but only checked once a day, a project starts on average half a day later than it could — across 20 accepted quotes a month, that is 10 lost half-days spread across a team, none of which shows up as a line item anywhere.
The double-invoicing failure mode is rarer but expensive when it lands: a credit note, an apology, and — worse for a small agency — a customer who now double-checks every invoice you send them, which is a trust cost that outlasts the actual money involved.
With Teamleader the first and most valuable decision is not technical: which system — Teamleader or a separate accounting package — actually owns invoicing, made explicit before any connection is built, not discovered afterward.
A connection needs two ends. Plenty of agencies will build you the API call and hand you a JSON payload; that is the easy half. The harder half is what the data lands in — a website, a webshop, a portal your customers log into, an internal tool that replaces a spreadsheet. JKC builds both ends, which is why the connections we build tend to keep working: nothing about the receiving side is a black box to us.
The connection itself: authentication, field mapping, rate limits, retries and a queue that survives the other system being down for an hour. Built against the documented API where there is one, and against whatever the vendor really offers where there is not.
WordPress sites that read from your systems instead of repeating them by hand: a careers page fed by your HR system, a team page that follows your payroll, prices and availability that are the real ones.
WooCommerce shops where the order is the last time anyone types it: it becomes an invoice in your accounting package, a label at your carrier, a stock mutation in your warehouse, and a line in your CRM, on its own.
When the process does not fit any standard product: a customer portal, a quoting tool, a planning board, a dashboard that reads three systems at once. Built on your data, with your systems as the source instead of a copy of them.
Built against the Focus API with a scoped OAuth grant. Webhooks on Deals and Quotations cover most of the "something changed" side without polling.
Web forms as Companies, Contacts and Deals (into the tool)
Matched on VAT or KVK number where available before creating anything new, placed in the right pipeline.
Quote accepted, as a trigger (out of the tool)
A webhook on the acceptance event that starts whatever should happen next — a project record, a planning notification, a welcome sequence.
Webshop orders as Deals or Invoices (into the tool)
Only if Teamleader is the agreed invoicing system of record — otherwise the order goes to the accounting package instead and Teamleader only receives the Deal for CRM purposes.
Invoice and payment status into a customer portal (out of the tool)
A logged-in customer seeing what is open and what has been paid, read straight from Teamleader instead of a status somebody keeps in a spreadsheet.
The same four steps every time, whichever tool it is. Nothing here is a workshop you pay for: step one exists because scoping a connection wrong is the single most expensive thing that can happen to it.
Not "which fields exist" but "which fields does somebody currently move by hand, how often, and what breaks when they get it wrong". Most projects turn out to need two or three flows, not a full two-way sync of everything. That conversation is what keeps the quote where it is.
A maintained connector from the vendor, a platform like Make or Zapier, or a custom integration against the API. Cheapest first, not custom first: if a supported plugin does exactly what you need, that is the answer and we will tell you so. Custom is for the cases where the off-the-shelf option would need so much configuring that it becomes the fragile option.
Every connection ships with retries, a queue and an idempotency key, so an order that arrives while the other side is down is delivered later rather than lost, and a retry does not create a second invoice. On a test environment first where the vendor offers one, so the first thing your real administration sees is a working connection.
Which alerts you will get, what each one means, what to do about it, and who to call. Plus the credentials in your own name, in your own vault — not in ours. A connection nobody but us can maintain is a connection you do not own.
This is the part most quotes leave out. A connection that stops working without telling anyone is worse than manual work, because with manual work at least somebody notices when it does not get done. Every connection JKC builds is monitored, and the monitoring is not an upsell — it is in the service fee.
A message that does not get through raises an alert the same hour, with the record it was about. Not a dashboard you have to remember to look at.
Anything that failed sits in a queue and can be sent again once the cause is fixed, in order. Nobody goes back through yesterday to find the four orders that did not land.
APIs get versioned, deprecated and rate-limited. When a vendor announces a change that affects your connection, adjusting to it is part of the service fee, not a new project.
For Teamleader specifically, the price hinges on that invoicing decision more than on the API work itself: a CRM-and-quotes-only connection is at the lower end of the range, while one that also has to reconcile Teamleader against a separate accounting package is closer to two projects than one.
A connection starts from €1,700 plus a monthly service fee, which covers the monitoring, the queue and keeping up with the vendor's API changes. Work outside a fixed scope is €95 per hour.
What moves the number is not the tool — it is how well the system on the other end is known. If JKC built your website, your webshop or your web application, we already know its data model, its edge cases and where its stock numbers really come from, and a connection into it is mostly configuration and testing. If it is a system we have never opened, we start with a short technical check of both sides and quote after that, so you are not paying hourly for us to work out the basics.
Two more things that move it, in our experience more than anything else: whether the tool has a real API or only a CSV export, and whether the sync has to go both ways. One-way is roughly half the work of two-way, because two-way means deciding, per field, which system wins when they disagree — and that decision is the expensive part, not the code.
There is no universal right answer, but there has to be one answer, agreed before we build anything. Teamleader is a reasonable invoicing system for a small service business that does not need much beyond quotes and invoices; a business with more complex VAT situations, multiple entities or an accountant already standardised on Exact or Moneybird is usually better off invoicing there.
Whichever you pick, the other system should only ever produce the deal or quote that feeds the invoice, never a second invoice of its own.
Yes, and it is a common shape for agencies and small manufacturers: a public shop for standard products, and a quote flow through Teamleader for anything custom or bulk, with both feeding the same Company records.
The main design decision, again, is which system invoices the B2B side — Teamleader's own invoicing, or the accounting package behind the webshop.
Webhooks cover most of what matters — deal stage changes, quote acceptance, invoice status — which is what makes Teamleader pleasant to build against compared to some of the older tools in this bank. A small amount of polling still covers anything without a webhook event, or as a safety net in case a webhook delivery is missed.
That safety net matters more than it sounds: a webhook that silently fails to deliver once is the same silent-failure risk as anywhere else, and the queue-and-retry approach we build every connection with catches it either way.
