For consultants
You know the business. I’ll build the system.
You know how businesses in your sector really work, and your clients already ask you what software they should be using. Partner with me and you can give them a system built around how they work. You run the conversations. I build it, put it live and keep it running, out of sight.
Jonathan PincasTwenty years in ERP. The platform, the builds and the hosting behind every partner’s clients.
One requirement, three hands
-
Your clientSays
“Temps get paid every Friday, but we invoice clients monthly. I want to see the margin on every placement as it happens.”
-
YouAgree it
Approved timesheets trigger weekly pay and build up on a monthly client invoice. Each placement shows charge rate, pay rate and margin, updated as timesheets are approved.
-
MeBuild & run it
Placement margin · week 41 Placement Charge Pay Margin Warehouse operative 18.50 13.20 28.6% Forklift driver 21.00 15.40 26.7% Live in their system.
You run the conversation. I run everything after it.
Building software around a business used to mean a team of developers. AI now writes the code, so the scarce skill is knowing what to build. That comes from someone who understands the business, which is you. Everything technical is my job.
Working out what to buildYouwith your client
You meet each client regularly, usually once a fortnight. They walk you through how the business really works, including the exceptions and workarounds, and together you decide how the system should handle them. Often that means questioning how something is done today rather than copying it. That’s the judgment your clients already come to you for.
You’re the client’s only point of contact. They deal with you, and I work behind the scenes.
Sessions run on a meeting tool built for this. An AI assistant follows the conversation, already knows the client’s system as it stands, and keeps a shared list of what you’ve agreed. You don’t need to know how the system is built, because the assistant does. After the session, your decisions become a precise written specification, and that is what I build from.
Building itMeon my platform
Every specification goes through a build pipeline I’ve engineered for ERP. The AI writes the code, automated quality checks hold it to account, and independent AI reviewers audit the work before it reaches the client. Changes go live shortly after you agree them, not at the end of a project phase.
- SpecificationFrom your session
- Build planBroken into steps
- AI buildCode generated
- Quality gatesAutomated checks
- Independent reviewAI reviewers audit the work
- LiveIn your client’s system
Running itMebehind the scenes
Once a system is live, I keep it running. You never have to think about servers or call a developer at the weekend.
- Hosting
- Professional servers in European data centres, with encrypted connections as standard.
- Backups
- Multiple independent copies in separate locations, including off-site.
- Monitoring
- Systems are watched continuously and raise alerts when something goes wrong. I usually know before anyone else does.
- Incidents
- I fix the problem and keep you informed throughout, so you can keep the client up to date.
How the arrangement works.
Your client contracts with you, and you contract with me. The client gets one relationship and one monthly fee, covering the sessions, the building and the running of their system. You keep a share of that fee every month the client stays with you.
Your client
Client- Gets a system built around how they work
- Owns the code from day one, and their data
- Pays one monthly fee, to you
You
Consultant- Own the client relationship
- Run the regular requirements sessions
- Decide with the client what gets built
Me
Platform- The platform, meeting tool and build pipeline
- Every build and release
- Hosting, backups, monitoring and incidents
Hosting and infrastructure are charged to the client at cost, with no markup. The commercial terms are simple and the same for every partner. Ask me for them.
| Advising alone | As a partner | |
|---|---|---|
| What the client gets from you | Recommendations | A working system, shaped by your advice |
| What happens to your advice | Passed to someone else to carry out, or not | Live in their system shortly after you agree it |
| How you’re paid | By the day or by the project | Every month, for as long as the client stays |
| Your place with the client | Until the engagement ends | At the centre of how their business runs |
Who this suits.
The best partners have spent years inside a particular kind of business. They know where the spreadsheets and workarounds are, and which of them matter. Technical knowledge isn’t required.
What you’ll bring
- Deep knowledge of how businesses in your sector actually run
- Clients, or a network of businesses that trust you
- The confidence to question how things are done, not just copy them
- Time for a regular session with each client
What you won’t need
- To write, or read, a line of code
- Developers, servers or a hosting contract
- To manage builds, releases or outages
- A software product of your own to sell
Typical partners:
Operations consultants Agency owners who’ve been through a build Sector specialists and advisers People who introduce businesses to better systemsQuestions.
Do I need to be technical?
No. Your job is understanding the business and deciding with the client what the system should do. The meeting assistant knows how the client’s system currently works, and anything that needs a technical view comes to me behind the scenes.
What happens when something breaks?
Monitoring alerts me, usually before anyone notices. I fix it and keep you informed, and you stay the client’s point of contact throughout.
What does the client own?
The code, from day one, and their data, which sits in a single database file. If they ever leave, they take both with them. Clients find that reassuring, and it makes the conversation easier for you.
What is the platform built on?
Go, SQLite, React and TypeScript: proven, open-source technology throughout, chosen because it lasts. There are no licence fees underneath and no vendor lock-in. Every client system is built on the same standard platform, which is part of why it’s reliable.
How are the economics shared?
The client pays one monthly fee to you, and you keep a share of it every month. Infrastructure is passed through at cost. The terms are the same for every partner, and I’m happy to go through them on a call.
How do we start?
Send me a note below, or book a call, about your sector and the kind of clients you work with. We’ll talk it through, and I’ll show you the meeting tool and a system built on the platform.
Know an industry inside out? Let’s talk.
A short note is the best way to start: your sector, the clients you work with, and what they keep struggling with. English or Spanish.
Prefer to talk it through? Book a call, or email jon@pincas.eu.
See what your clients would get: the two-page overview PDF
Based in León, Spain. Working with partners and clients across the UK and Spain.