OFF-FORMAT
Got a problem the right software doesn't exist for yet?
Tell us about it. We read every request ourselves. If we can build something that genuinely makes sense for your business, we reply and explain how we'd approach it. If we can't, we tell you so clearly.
You don't need to know which category your problem falls into. We read the brief, work out what's underneath, and decide whether software is the right answer. We take on few projects outside the five services, and only when the problem is clear.
FROM BRIEF TO DECISION
Two example briefs, written by us to show the method: they are not exchanges with real clients. Pick one and see how we read it.
Illustrative scenario
The problem, as it arrivedExample brief · not a real client
- FROM
- founder · B2B fintech · 18 people
- SUBJECT
- AI Act risk class + 90-day plan
We assess credit requests for SMEs with an AI model in production since 2023. We fall under the AI Act, but we and our lawyers disagree on the risk class. We need a clear technical opinion and a 90-day remediation plan, not a 200-page audit nobody reads. Our compliance lead can work alongside you. Budget is flexible if the scope is tight.
What we understood
The system
A model that already decides on credit: the technical side exists and needs documenting.
The real blocker
What's missing isn't an audit. It's a shared position between the team and the lawyers.
The result needed
A short document you can decide with, plus a plan with dates.
The constraint
Limited time and attention: no huge deliverables.
What could be built
A technical assessment of the model (data, decisions, traceability) mapped to the AI Act requirements, a log of the model's decisions, and a prioritised 90-day plan. This is not legal advice: the legal classification stays with your lawyers, we provide the technical basis.
The decisionYES
Worth building. Proposal: three intensive days with your team, a technical memo in week two, then the plan. Outside Services 01–05, sized to this brief.
- The problem, as it arrived
- What we understood
- What could be built
- The decision
HOW IT WORKS
- 01
Send us the problem
Half a page is enough: what happens today, what's blocking you, what you've already tried.
- 02
A clear answer
If there's a good fit, we explain how we'd approach it and what could be built. If there isn't, we tell you so and explain why.
- 03
A call to define the project
If it makes sense to go ahead: an in-depth call, from which the written scope of the work comes out.
- 04
The build
We work remotely and come to you when it helps. Timing, way of working and cost are set in writing, project by project.
WHAT WE DON'T TAKE ON
Whatever the budget.
- One-off copywriting or content production
- Automation with no AI component
- Hiring or staffing requests
- Copies of software that already exists
- Installing generic chatbots
IF YOUR PROBLEM ALREADY HAS A NAME
- 01Operational product buildsA process rebuilt as software that runs it.
- 02Agent infrastructureAgents that work together and can be inspected.
- 03Editorial AIOne source, many formats, your voice.
- 04Founder co-pilotDecisions made with the full context.
- 05Audit & rewriteWhat to keep, fix and rebuild in your AI.
NEXT STEP
Send us the problem →Write it the way you'd explain it to a colleague. We read it ourselves and reply with a yes or a no, and the reason.