Hands-on software and AI engineering
Technical direction and implementation for your next product, your prototype or the software you already run.
Available from January 2027. Let's discuss your plans now.
Build a new product
You have a product idea or a business need and want someone to define a useful first version and build it. You do not need an existing engineering team.
Typical starting points include an internal tool replacing spreadsheet-based work or the first version of an AI product.
How I help
- Define the scope and architecture for the first release and likely next steps.
- Build the application, APIs, data processing or AI components, reviewing working versions together.
- Set up automated checks and deployment as part of implementation.
You get: Working software covering the agreed features, repeatable deployment and setup and architecture notes for future maintenance.
Take a prototype into production
Your prototype demonstrates the idea. You need to close the engineering gaps before people can rely on it.
This could mean turning a notebook or demo into a deployed service, or preparing an application for its first customer rollout.
How I help
- Review what can stay, agree release criteria and identify the work needed before rollout.
- Implement access control, failure handling, automated deployment and monitoring. Test realistic workflows and failure cases.
- For AI systems, evaluate model behavior, cost and reliability on representative inputs and address the gaps.
You get: A deployable product meeting the agreed release criteria, repeatable releases and an operational walkthrough covering any remaining limitations.
Improve an existing system
Your software is slow, unreliable or difficult to change. Parts of it may be poorly understood, or the development process may make even small changes harder to deliver than they should be.
How I help
- Reproduce failures and profile bottlenecks in APIs, database access, data pipelines or memory use.
- Understand unfamiliar components, simplify difficult code and replace unreliable integrations.
- Plan and implement framework and dependency upgrades, checking for breaking changes, deprecated APIs and regressions.
You get: Implemented improvements with regression checks, before-and-after measurements where relevant and a walkthrough of the changes and recommended next steps.
Engineering workflows
This can also be a focused engagement: improve tests and CI checks, build and dependency tooling or prepare repositories for coding agents. The work can include documentation, agent instructions and review practices.
You get a repeatable development setup and documented conventions. We use it together to verify that it addresses the delivery problems and can be maintained.
Read about my approach to engineering workflowsHow engagements work #
We can work on a defined project or an ongoing technical engagement. I work remotely and join you on site for workshops, kickoffs or focused implementation weeks.
- Free 15–30 minute briefing. Discuss your situation, goals and existing plans. You get a recommended next step and, where the work is clear, a rough scope.
- Agree scope and involvement. Set completion criteria, timing and weekly involvement. If deeper investigation is needed, we can start with a separate paid assessment.
- Build, verify and share knowledge. Deliver working changes, verification and documentation. Review progress together and hand over the work or agree the next priorities.
Discuss your project #
Available from January 2027. Tell me what you want to build or improve and your timeline.