01
Start with 30 minutes.
Every service begins with a discovery meeting. We listen, map the real problem and define a useful first outcome.
THOUGHTFUL FROM THE START
A good conversation.
A better way forward.
We connect creative craft with technical depth.
And keep the work grounded in what your business needs.
02
Give it form.
Design, build and connect. Test the details and the difficult handoffs.
03
Make it yours.
A working system, source and a clear handover. Then keep improving.
BUILT TO BELONG TO YOU
The result.
And the way to own it.
- Source and deliverables agreed in the scope
- Access to your accounts and systems
- Documentation of the work and dependencies
- A demonstrated acceptance and handover
- A clear route to care and improvement
A POSSIBLE WORKFLOW
01Product brief
02Designed workflow
03Working release
04Your source & keys
One job, from first input to finished handoff.
BEFORE WE BEGIN
A few clear answers.
How do fixed fees work?
We agree the deliverables, integrations, review rounds and acceptance criteria before the fee is set. You see what is included, what you need to provide and which external costs are separate.
Can I start with one project?
Yes. Start with a scoped build or a focused discovery milestone. Ongoing care and improvement plans are available when there is a recurring job to do.
What happens if the scope changes?
We identify the change and agree a new milestone or adjustment before the additional work starts. A flat fee always belongs to a clear scope.
Do I own the result?
Ownership and handover are included in the project scope: source, documentation and access to the appropriate accounts and systems. Third-party licenses retain their own terms.
Can you work with the tools I already use?
That is part of the scoping process. We assess the APIs, access and practical limits of the tools involved before committing to an integration.
Can we work with private or local AI?
Yes. We can scope local models, private knowledge systems and the hardware or hosting they need. The deployment and data boundaries are defined around your requirements.
Are hardware, ad spend and usage included?
The proposal identifies them explicitly. Hardware, travel, paid software, ad spend and model or telecom usage are either listed separately or covered by a stated allowance.