Plug&Pay builds high-performing funnel software designed to optimize conversion for their customers. Their platform allows users to build entire sales funnels, from landing pages and checkouts to upsells and invoicing, using the latest techniques to ensure optimal performance and growth.

They are the number one payment processor in The Netherlands and Belgium processing more than €1B in turnover for their customers.

For the engineering team at Plug&Pay, building high-performance funnel software requires a high-performance development environment. But their workflow had become fractured. To get the job done, engineers were juggling a disjointed stack: Cursor for the front end, Claude Code and Augment Code for generation, CodeRabbit and BugBot for reviews, and Perplexity Pro for research.

The AI drag was tangible. Review tools like BugBot had become a burden rather than a help, flooding Pull Requests with noisy, verbose comments that annoyed the team. Meanwhile, engineers had to manually copy-paste context into Perplexity to debug Dockerfiles.

Worse than the operational inefficiency was the risk associated with opaque billing. The team watched as tools they relied on shifted from unlimited requests to limited credits with abstract costs and random markups. They were facing a “rugpull strategy”, getting locked into a workflow only to have the pricing model change overnight. They needed stability, transparency, and a tool that wouldn’t penalize them for scaling.

“Before Kilo, I was constantly context-switching and copy-pasting code to debug. It was slow and error prone. Kilo lives right in my IDE and understands my entire infrastructure setup. It knows exactly where to look to solve architectural challenges without me having to feed it context.”

The decision to switch to Kilo Code wasn’t just technical; it was philosophical. In an industry of silo’d tools and black-box pricing, Kilo offered a unique proposition: an all-in-one platform that integrates seamlessly with tools devs already use (JetBrains, VSCode, CLI, etc.) and provides unified billing based on transparent usage metrics.

“We watched other tools shift from unlimited requests to abstract credit models overnight with random markups. It felt like a bait-and-switch. We needed a partner, not just a vendor. Kilo gave us stability. We pay for what we use, without hidden costs.”

What tipped the scale was the trust factor. Plug&Pay wasn’t just buying software; they were investing in a team that reinvested in the open-source community. This aligned with Plug&Pay’s views about the AI landscape. They are betting that open source will win the race in the long term.

Implementation didn’t just replace tools, it changed the team’s velocity. Kilo acted as the unifying layer that molded to every workflow, whether it was backend developers building API endpoints, or the DevOps team rewriting IaC resources.

The “Aha!” moment came when people started using Kilo and this drove a culture change. Developers were previously resisting AI because it required them to switch their routine by moving to a completely new IDE or terminal experience. Because Kilo integrated smoothly with familiar tooling and intelligently knew where to look without manual context dumping, the friction vanished. Developers became AI-empowered within their existing workstream.

“Kilo is like dough, I can mold it to fit my specific workflow in JetBrains or the CLI without fighting the tool. It doesn’t force me into a box; it adapts to how I code.”

The result of the switch was an all-in-one, agentic engineering platform to complement a high-velocity engineering culture. Plug&Pay replaced their fragmented stack with a single, powerful platform that rapidly became the standard, driving 80% adoption across the engineering team with Kilo Code Reviews enabled on all active repos.

“Before I push to remote, I have Kilo to sanity-check my logic. It catches issues I might miss. Then Kilo Code Review ensures every PR is clean and ready to merge. It gives me the confidence to ship faster.”

The promise of unified billing held true: one tool, one invoice, and total predictability. But the most significant ROI has been the agility of the partnership itself. Unlike other vendors where support tickets stagnate, Kilo operates at “Kilo Speed.” When the Plug&Pay team finds a bug or requests a feature, Kilo often ships the update within 24 hours ensuring developers don’t lose momentum.

For Plug&Pay, the chaotic noise of managing multiple subscriptions and debugging billing statements is gone. In its place is a partnership that moves as fast as they do.

“Kilo is responsive to feedback and ships updates at ‘Kilo Speed’. The stream of new features is like Christmas for developers all year round.”