Enterprise AI consulting from partners who write code
You have
A board that wants AI on the roadmap, a list of ideas, and maybe an RFP for an AI consulting partner. What you need is a partner who turns the plan into working software.
You worry about
- A plan on slides that nobody builds
- AI pilots that never reach real work
- Money spent on AI with no clear return
- Company data going to an outside AI service
- New tools your people do not use
- A transformation too big to start
We give you
A partner for your AI adoption
A senior engineer who writes code and leads our engineers
Step 1usually $5,000–30,000
Studies one department or system and writes down which work to automate with AI first, in 2 to 4 weeks. The adoption map is yours.
Step 2, if you continuemonthly, priced after step 1
- Builds it with our engineersWhat to build is written down first, AI writes code against it, and an engineer reads every change. Part of the monthly work led by a partner. The hours it includes and its price are in our written offer before we start. If a month needs more, we tell you first, and you decide.
- Checks every release before it goes liveAn engineer reads every change, and the automated tests must pass. Before each release, you get it in writing: it can go live, or not yet. Part of the monthly work led by a partner. The hours it includes and its price are in our written offer before we start. If a month needs more, we tell you first, and you decide.
- Trains your people to run itFirst the basics of working with AI safely, then your own tasks, with us next to them. Part of the monthly work led by a partner. The hours it includes and its price are in our written offer before we start. If a month needs more, we tell you first, and you decide.
You get
- A written AI adoption map, ranked by return
- AI working inside the systems you have
- Your people able to use AI and run it
- The 30-minute call is free
- You can stop after the first step
- Nothing starts until you say yes
How it works
Our AI consulting ends in working software. First we learn how the work is done today: we talk to the people who do it and read the systems behind it. You get a written map of which work to automate with AI first, in what order and at what return.
Then the same partner builds it with our engineers, using AI coding tools such as Claude Code and Cursor that read and write code, and an engineer reads every change. AI enablement is part of the work: your people learn first how to use AI safely, then on their own tasks, with us next to them.
If your company chooses an AI consulting partner through an RFP or a procurement check, tell us which documents it needs. We answer each one in writing before you sign anything.
This is for you if
- The board wants AI on the roadmap, and the risk of getting it wrong is yours.
- You have AI ideas and need a partner who decides with you and also builds.
- Your company chooses partners through an RFP or a procurement check.
- Your people need to learn to work with AI.
- You want to start small: a first step one person can sign, before any large program.
Ways to start
A first step usually costs $5,000 to $30,000 and takes 2 to 4 weeks. The price depends on the size of what we study. We fix its scope and price in writing before we start. The report is yours, even if you stop there.
AI adoption study
One department or one system. We check how ready it is for AI and map which work to automate with AI, in what order and at what return. You get an adoption map and a ranked plan.
Legacy system diagnostic
A map of what depends on what, the code nobody uses, the business rules found in the code and written in plain words, and what a migration would cost. We work from a copy of the code, your documents and interviews, not on the live system. You get a picture of the system that no longer depends on the people who remember it.
Prototype on your data
A working prototype on a copy of your data that you choose to share, so the decision to build rests on facts, not on slides.
How a partner leads the work every month
Every month after the first step, if you continue: a partner and the engineers your plan needs. The hours and the price depend on what the first step finds, and they are in our written offer before the monthly work starts.
Decides with you what to change firstPart of the monthly work led by a partner. The hours it includes and its price are in our written offer before we start. If a month needs more, we tell you first, and you decide.
In the order that pays off soonest and puts the least at risk.
Writes code and leads our engineersPart of the monthly work led by a partner. The hours it includes and its price are in our written offer before we start. If a month needs more, we tell you first, and you decide.
With engineers whose work we know. What to build is written down first, AI writes code against it, and an engineer reads every change.
Checks every release before it goes livePart of the monthly work led by a partner. The hours it includes and its price are in our written offer before we start. If a month needs more, we tell you first, and you decide.
Before each release, the engineer who checked it tells you in writing: it can go live, or not yet.
Trains your peoplePart of the monthly work led by a partner. The hours it includes and its price are in our written offer before we start. If a month needs more, we tell you first, and you decide.
First the basics, then your own tasks with us next to them. Your team runs what we built.
A written report every month
What changed, what is still open, and what we would do next.
Everything stays yours
The code, the written specifications and the documents are yours and keep working without us.
What we bring to a company with legacy systems
We have worked inside large companies
Our senior partners spent 20+ years inside large companies, as project leads and CTOs, on budgets of millions and with teams of up to 50 engineers. They moved old systems to new ones and brought new tools into teams that did not want them.
We also build products fast
We build and run products of our own, such as ExoChat, our engine for AI assistants. Nine of our engineers also built and run a subscription streaming platform for a client, under NDA: every change traces back to a written requirement, and any release can be rolled back together with its database.
We work with AI every day, and our method is open
AI is part of every step of our work: requirements, prototypes, design, code, tests, review and documents. We know where AI is strong and where it makes mistakes, so an engineer checks every result. Our method, spex, puts what to build in writing first, and engineers check what AI builds against it. You do not need to read it yourself: spex on GitHub
Our engineers grow with us
A partnership since December 2016, out of a team that has worked together since 2008. Now 100+ developers in 20+ countries: the partners, the people we grew ourselves, and the teams we have delivered large projects with before. We teach them our stack, how to work with AI, and our own methods, so we know what each engineer can take on.
35+ projects behind us
Fintech and payments, telecom and VoIP, logistics, business systems, social platforms with 10M+ users. Our team has worked with SAP since 2007.
The partner who leads also writes code
The partner who leads your work writes code. Their income depends on your project: they get a percentage of what we earn on it. Nobody sits between you and the engineer.
What we do not do
These rules keep your systems safe and keep the work yours.
We do not need your live systems to start
The study and the diagnostic work from copies, documents and interviews. The prototype runs on data you choose to share.
We do not let AI change your systems unchecked
No change goes live until the automated tests pass and an engineer has read it. Releases are automated, and any release can be rolled back.
We do not keep your code or data
When the work ends, we delete our copy and ask you to remove our access.
We do not rewrite everything at once
We change one part at a time and plan each change so the systems your business runs on keep working.
We do not sell you a platform
You pay for the work, not for licenses. The code and the documents are yours.
We do not make you depend on us
We train your people, and everything we build is written down. Your team can run it without us.
Work we can show
Work for banks, telecom operators and large companies, on the systems they run every day. Client names stay private.
- For banks we built a system that digitizes and stores scanned documents. Document storage
- Our team has worked with SAP since 2007: business processes and BI on SAP for telecom operators, retailers and banks. We also built a mobile platform that works with SAP: business apps built from ready components, with offline work. Mobile platform
- For a large corporation we built a system that works out what a product should cost, given exchange rates, availability and special terms. Cost calculator
- We built fleet monitoring for a telecom company, integrated with its ERP. Fleet monitoring
- We took over a running logistics CRM/ERP from its previous developers with zero downtime, together with its delivery and payment integrations.
Questions before you book
- Will you sign an NDA?
- Yes, before we see anything. You can send yours or use ours.
- Who will I sign the contract with?
- With one of the companies in our group. We sign contracts in Europe, the US and other jurisdictions, and we choose the country by where your company is. You get the company's name, country and registration before you sign anything. We work in English.
- Who owns the code?
- You do.
- Where are you?
- Around the world: 100+ developers in 20+ countries, in Europe, the US and Asia. We work with clients in the US and Europe.
- Is the first step free?
- No. It is real work by senior engineers and usually costs $5,000 to $30,000, with the exact price in writing before we start. The 30-minute call before it is free, and on it we tell you honestly whether you need it.
- What if the work turns out bigger than we thought?
- We tell you before any extra work, and nothing more is charged unless you say yes.
- How soon can you start?
- The first step usually starts within a week after we agree. The monthly work starts only after it, if you say yes.
- Where is our code while you study it?
- On a copy you give us. We do not need your live systems. Before we start, we agree with you in writing which machines hold the copy and which AI tools read it, and you can say no to any of them. When the work ends, we delete the copy.
- Can the AI models run inside our infrastructure?
- Yes. Open-weight models can run in your cloud or on your own servers. We have run them in production next to hosted AI services.
- Will you work with our procurement and security checks?
- Yes. Tell us which documents they need. We answer each one in writing before you sign anything.
Talk to the partner who would lead it
A 30-minute call about your systems, without a sales presentation. Tell us what runs your business and what you want to change with AI. You do not need to prepare anything. After the call, you will know which first step makes sense, or that none does yet.