The security questionnaire, answered in public
We publish our security questionnaire answers so clients see the real controls, gaps and limits before procurement asks.
ReadInsights
Practical notes on AI-first engineering, software architecture, security and delivery, written for the people who have to decide what gets built and who pays for it when it goes wrong.
We publish our security questionnaire answers so clients see the real controls, gaps and limits before procurement asks.
ReadRetrieval quality sets the ceiling on every answer. Most teams tune the model while the index keeps returning the wrong material.
ReadYou spent a decade learning to manage software supply chain risk. Then a model provider arrived with none of the properties that made those…
ReadEscrow fails when money can sit in two states at once. Model every state, transition, retry and ledger entry clearly.
ReadPrompt injection is a privilege problem, so defenses must limit what AI systems can do rather than rely on better prompts.
ReadAI has cut some freelance categories, grown others, and changed many more. The split depends on whether buyers can judge the work.
ReadUtilities need software choices that can be maintained, audited, rebuilt and handed over across twenty year horizons.
ReadMarketplace reviews keep workers tied to a platform. Portable records need verified facts, signatures, attribution and revocation.
ReadThe real asset is permission to show content. Your CMS needs rights, expiry, takedown and reporting built into its model.
ReadDisputes need structured agreements, timers, defaults, partial outcomes and human accountability when money is on the line.
ReadNext step
A senior engineer reads every enquiry and replies within one business day with an honest assessment, including when we think you shouldn’t build it. No sales call, no deck.
Certified, partnered and awarded









1/7
Discuss your project
Seven short questions. About 90 seconds. A senior engineer reads your answers before we reply. No sales sequence, no newsletter. Just a thoughtful response about what comes next.
Start here
Choose the one that comes closest.
The problem
A sentence or two is enough. Tell us what isn’t working today or what you want to make possible.
Where you are today
Choose everything that applies.
Timing
A real deadline changes how we approach the work. If there isn’t one yet, that’s useful to know too.
Scope
A range is enough. It helps us understand the right approach and team for the problem. It does not determine what we charge.
Your team
This helps us understand whether we should lead the engineering, work alongside your team, or advise your existing engineers.
Stay in touch
A senior engineer will read what you’ve shared and respond within one business day.
How would you prefer to continue?
Received
A senior engineer will review what you’ve shared and come back with the most useful next step.