What we assess together
- Can users complete the agreed task?
- Are outputs supported by the right sources and checks?
- Do access rules and review steps behave correctly?
- Are latency, operating cost and failure handling acceptable?
How we work
Know what you’ll receive.
Agree how we’ll test it.
A founder-led engineering engagement with explicit deliverables, review points and handover.
A clear scope.
A reviewable result.
Work directly with the founder, from the first technical review through implementation and handover. Scope and availability are agreed individually.
- 1 / Understand
Inspect the existing system.
Review the task, current tools, sample data and access. Recommend configuration when it is enough.
- 2 / Define
Agree what “done” means.
Set the deliverables, exclusions, acceptance cases, fees and milestones before implementation.
- 3 / Build
Review working software.
Develop a bounded feature, demonstrate progress and test both useful outputs and failure cases.
- 4 / Handover
Leave an operable system.
Deliver agreed source code, configuration, test evidence and operating notes. Define ongoing support separately.
What you receive
before a build begins.
A paid discovery produces a written decision and an implementation brief. You can review the scope before committing to development.
- System assessment
- The current workflow, relevant architecture, accessible data and existing tools that may already solve the task.
- Implementation brief
- The user journey, proposed connections, deliverables, dependencies and exclusions.
- Acceptance plan
- Representative examples, failure cases and agreed measures for correctness, access, latency and operating cost.
- Commercial proposal
- Fees, milestones, review responsibilities and handover scope. Optional support is priced separately.
Decide what to build.
Then commit to delivery.
Discovery can recommend an existing product, a conventional integration, an AI-assisted workflow or an agent feasibility study. The choice depends on the task and evidence, rather than a predetermined technology.
When implementation is justified, we agree milestones, acceptance cases, dependencies and exclusions. Changes in scope are discussed before additional work begins.
What handover includes
- Agreed source code and configuration.
- Test results and known limitations.
- Operating notes and dependency costs.
- Separate scope for monitoring, support or further features.
Commercial responsibility
Engagements are priced for agreed engineering work. We do not tie fees to sales commissions or promise business profitability. The feature should have a clear purpose for your team; we remain accountable for the agreed implementation and acceptance criteria.
Before you commission the work.
Do we need to replace our existing application?
We assess your current tools and data first. The scope may be an integration, a feature in existing software or a new application. A replacement is considered only when the requirements justify it.
How are projects priced?
Discovery is scoped and priced first. Implementation fees follow the agreed technical scope, dependencies and acceptance criteria. There is no universal subscription or revenue-share fee. Changes and ongoing support are agreed separately.
What happens to the code and running costs?
The proposal states which project source code and configuration you receive and the terms for existing components. Hosting, model, messaging and other vendor costs are identified separately. Ownership and licensing terms are agreed before work begins.
What if an existing tool already solves it?
The recommendation can be configuration or an existing product. A discovery does not require you to commission custom development.
Scoped AI engineering
Have a task in mind?
Let’s assess the fit.
Start with the work, the information it needs and the question you want to answer.