Forward-deployed engineers who know how your customers' business runs.

What the service is.

We work inside your team, on your product and with your customers. The work usually covers:

• Choosing the use cases worth building. Which problems in your customers' business have an answer they will pay for and sign off, and which are better left to a spreadsheet.
• Building them. We write production code with your engineers, in your product.
• Setting the test. Acceptance criteria and test cases your customer's people would actually check: month-end cut-off, intercompany sales, cost allocations, a batch that was reworked, a promotion that overlapped a price change, a forecast after a stock-out.
• Checking the output against the real business. How a ledger, a plant or a planning cycle actually behaves, which is often different from what the documentation says.
• Being in the room. When your customer's finance director, sales director or head of supply chain pushes back, we answer on your side of the table without needing a briefing first.
• Helping it stick. Working with your customer on the routines that have to change for the software to be used after go-live.

Where we know the business.

We know how manufacturing, FMCG and consumer-goods companies run across all of their key processes, well beyond the finance function: new product development, sales and key accounts, revenue management and pricing, demand planning and S&OP, operations and production, procurement and supply chain, human resources, finance and strategy. We have built software for each of them ourselves, so we know where a use case gets tested and what a customer is likely to question.

What we have built for each process →

You have probably heard some of these.

• “The demo went well. Then their group controller asked how we handle intercompany, and the room went quiet.”
• “Their head of supply chain asked how our forecast treats promotions and stock-outs, and nobody on our side could answer.”
• “We can't tell whether the output is right, so we can't tell the customer it is.”
• “The pilot produced a number that disagrees with their ledger, and now the whole project is under review.”
• “We're building the feature the loudest customer asked for, and we can't tell whether it's the one worth building.”
• “Our engineers are excellent, and none of them has ever run a planning cycle or closed a month.”

How the work is shaped.

There are three usual shapes. Each is scoped with you and quoted per engagement, in writing, before anything starts, and the scope names what you keep.

Use cases, scoped. We rank the use cases with your product team, check the data each one needs, and write each one up with its acceptance criteria, ready to build. You keep the specifications and the test cases.

One use case, built and tested. We take the most valuable use case through to something your customer's people use: built with your engineers, tested against the acceptance criteria, with the controls around it. You keep the working feature and the tests behind it.

Forward deployed. We work with your team and your customer's for longer, building, deploying and helping change the routines the software depends on.

How we work with you.

• We check before we say yes. When we tell your customer a figure is right, it is because we have checked it. That is what makes it worth having us in the room.
• Your team owns the model. Your engineers and data scientists own the model and how it is trained. We make sure the answers it gives would stand up in front of a finance director or a head of supply chain.
• We work as an independent company alongside your team, and your customer knows who we are.
• Your customer's data stays in their hands. We work with it only as far as the scope and your contract with them allow, and we never use it to train models.