An agent here is one workflow that runs without anyone opening a tab. Not a chatbot on your site, not a Zapier scenario with a model in the middle, and not a pilot that needs a second engagement to reach production.
Enriches every inbound lead, scores it against an ICP file the sales team edits themselves and routes the hot ones into Slack. No-fit demos fell from about half of bookings to about a fifth.
Case studyRead the full buildParses each application, matches it against the open roles and cards it into the right recruiter’s DM with a match summary attached. First response went from 38 hours to 4.
Case studyRead the full buildStefan H. · Founder, TalentbridgeThere was a senior backend guy one of our clients had been chasing for about six weeks. He came in through our own site on a Tuesday and I got to his CV the following Monday. He’d already accepted something else by then, which I only found out when I emailed him.
We’re usually back to candidates the same day now instead of two days later.
We map the workflow as it runs today and put the scope in writing before any code exists. You get a fixed quote against that document.
Code runs against your real data before handover and transfers to you on final payment. That is how the RevSync build surfaced that their ICP rules lived across three Notion pages contradicting each other.
Documentation, a walkthrough and the API accounts in your name on final payment. The builds above ran 8 to 10 working days end to end.
If the workflow changes shape every quarter the agent is out of date before it earns back the build, and if the vendor’s compliance posture is the actual product, as with payroll or e-signature, you should keep buying it.
That is a maximum rather than a fixed price. You are billed monthly on the hours the build actually takes and the invoice never passes the number agreed in writing before anyone writes code. Fewer hours than planned and you pay less. More hours and that is on me. The 30 minute call is free and so is the written scope that follows it, which is yours whether you hire us or not. What runs afterwards is the API bill rather than a licence. Replacing a tool you pay for every month is Lane 02 and is priced there.
A working agent deployed to your infrastructure, with documentation your team can extend from. The repository, the deployment and the API accounts go into your name on final payment. For us that means one workflow automated end to end rather than a platform subscription. The scope is fixed in writing before any code is written.
One agent doing one recurring job costs up to €3,000. That is a maximum rather than a fixed price. You are billed monthly on the hours the build actually takes and the invoice never passes the number agreed in writing before anyone writes code. What you pay afterwards is the API bill rather than a licence. A system that replaces tools you subscribe to sits in Lane 02 and is priced on the business process automation page.
Most agents ship in 2 to 4 weeks. The published builds took 8 working days for RevSync’s inbound qualification agent and 10 for Talentbridge’s CV routing. A system replacing several tools at once takes longer. The Stratify build ran 5 weeks across four modules and sits in Lane 02.
Claude Code runs the reasoning steps and the rest is chosen per build, so a deterministic routing rule ends up as a rule file the client edits rather than a model call, and a scheduled job ends up on a cron in the client’s own repository. What you are buying is an agent that works on your data rather than a stack we happen to like.
Everything the build runs on, in your name, on final payment. No per-seat licensing and nothing to renew. What you pay afterwards is the API bill.
That is what the handover is for, and it has happened on the published builds. The OpsQuanta ops lead added churn cohort analysis and a cash-runway alert without us, and the Stratify engineers extended their system twice in eighteen months.