AI Agents & Automation
Custom agents, tool pipelines and automation that run inside your product — not a chatbot bolted on the side.
- 01Agent runtime
- 02typed tool layer
- 03retrieval memory
- 04metered AI usage
CAPABILITIES
He builds AI-integrated products end to end — agent runtimes, mobile and web apps, admin dashboards, and the APIs behind them.
Custom agents, tool pipelines and automation that run inside your product — not a chatbot bolted on the side.
One codebase, iOS and Android, with the backend and the panel that runs it.
The screen your team actually works in all day, priced by what is behind it.
Everything beyond the two fixed products is quoted after Discovery, as one fixed price for the whole build. A number with no scope behind it is not a quote — it is an anchor, and it is the reason you will not find one published here.
A single-purpose portfolio site, priced flat — no unit counting. It is this cheap because you provide the content.
A one-page business site, priced flat — no unit counting. Same trade: the price holds because the content is yours.
A predictable, modular approach to software delivery. No surprises, just milestones.
We go through the requirements, count what actually has to be built, and choose hosting and frameworks. Either an online call or the onboarding form plus a description of the project.
Those counts run through one weight table that produces both the fixed price and the timeline, so the two can never disagree.
The panel you will run the business from is designed first, because it defines what you control; every other screen derives from it.
You say "this is what I want" and the v1 decisions freeze. After this point any change, even mid-build, is a priced change request.
Wired to exactly what the confirmed frontends need — nothing more — plus any work that sits behind no screen at all.
You review the working v1. On bigger builds this is the integration review, because the screens were already signed one by one.
Defects, meaning behaviour that does not match the approved spec. New features are change requests, and that boundary was agreed before anything was built.
Review, fix, review until submission. Handover is training, documentation and the source on final payment, followed by 30 days of free bug fixes.
Every build includes a free 30-day window for genuine bugs — delivered behaviour that does not match the approved spec. After it you either take a care plan, priced as a percentage of the build per year, or pay per incident.
Every delivery comes with 30 days of free fixes for any behavior not matching the approved specification.
Monitoring, security patches, backups, and bug fixes in delivered scope.
Care, plus two hours of changes a month and priority response.
Care+, plus five development hours a month and proactive improvements.
Prefer pay-as-you-go? Pay per incident at a fixed hourly rate on a best-effort basis. Subscribers receive guaranteed SLAs and priority queueing over ad-hoc calls.
End-to-end infrastructure management so you never touch a server. Deployment pipelines, cloud scaling, backups, and SSL certificate maintenance handled for you.
Every project is scoped individually and quoted as a fixed price before any code is written. Two things have a published price because they are fixed products: a portfolio site at $100 and a one-page business site at $250. Everything else is priced out of Discovery, which is free — an online call or the onboarding form plus a description of what you want built.
The timeline comes out of the same scope model as the price, so the two never disagree, and you are quoted the buffered number rather than the optimistic one. For reference: a business platform with an 18-tab admin panel, a client portal and payments took under four months.
A paid Discovery session to agree what is being built, then decisions at four points: the fixed quote, the design lock, each milestone sign-off, and handover. For the $100 and $250 fixed products you also supply all the content. Milestones are signed on working behaviour you can see, not on code you cannot read.
Before the design lock, each phase includes two rounds of minor revisions. After the lock, changes are handled as Change Requests: assessed for time and cost, and approved in writing before work starts. The boundary is agreed before anything is built, which is the point — a rule agreed in advance cannot turn into an argument later.
Yes — the source of your project is yours on final payment. Two things stay as they are: my pre-existing tooling and frameworks remain mine, and you get a perpetual licence to use them as they are embedded in your project; and open-source components come to you under their own licences.
There is a free 30-day window after delivery for genuine bugs — behaviour that does not match the approved spec. After that you choose: a care plan priced as a percentage of the build per year (Care 12%, Care+ 18%, Partner 24%), or per-incident support. New features and changes of mind are Change Requests either way.
Replies within 24 hours