How I can help
From a first version to an AI workflow running at scale, these are the four things I'm asked for most. If yours doesn't fit neatly, ask anyway.
Build your first version
Take an idea from a rough brief to a launched product, with the unglamorous parts done right: login, payments, email, analytics, error tracking and hosting.
A good fit if
- You have an idea and want one engineer to own the whole build.
- You need it live in front of real users, not just a demo.
- You want it built so another developer can pick it up later.
What you get
- A scoped plan for the first version, and a list of what can wait.
- The product built end to end: database, backend, frontend, login, payments, email, analytics and error tracking.
- Deployment, documentation and a clean handover.
Rescue an AI-built prototype
Take over a codebase built by AI tools, cut what isn't used, fix the structure and the data model, and make it safe to change.
A good fit if
- AI tools wrote most of your code, and every change now breaks something else.
- Nobody can explain how parts of it work.
- You want to keep what works instead of starting over.
What you get
- An audit of what is actually used, what is risky and what can go.
- A cleaner structure, often a monorepo with clear boundaries between the marketing site, app and server.
- A rebuilt data model with proper relations, and queries that perform.
AI workflows and integrations
Build the pipelines that read documents, extract data, match records and keep systems in sync, including systems with no public API.
A good fit if
- Your product reads documents, extracts data or makes recommendations.
- You need to know how accurate it is, not guess.
- You need to connect to other systems, some of them without a public API.
What you get
- OCR and extraction pipelines, for example on Azure Document Intelligence.
- Matching and recommendation systems using embeddings and vector search.
- Scheduled syncs, SDKs and API integrations, covered by tests.
- APIs your own enterprise customers can build on.
SeeIENA matching engine, Tax Notice Pilot, TheCampStack SDKs, myTpen
Security and enterprise readiness
Get your product ready for enterprise security review: policies, technical controls, evidence and the SOC 2 process.
A good fit if
- An enterprise prospect sent you a security questionnaire.
- A customer asked whether you have SOC 2.
- You want controls built into the product, not only written down.
What you get
- Security policies and control documentation.
- Technical controls implemented in your product.
- Preparation for the audit and its observation window, alongside the auditor you choose.
I'm not an auditor. I get you ready for one. I'm currently leading a SOC 2 Type II program for Tax Notice Pilot, which is in its observation window.
SeeSOC 2 readiness checklist for small software teams, Tax Notice Pilot
How a project starts
1.A free call
We talk through what you have, what you need, and whether I'm the right person for it. No pitch.
2.A written scope
I send a short plan: what I'll build or fix, what I'll leave out, how long it takes and what it costs.
3.The work, in small steps
You see progress as it happens, and decisions are written down so nothing lives only in my head.
I don't sell fixed packages. Every project is scoped after the first call, so you get a clear estimate for a defined piece of work.
Book a free call