Most AI products die between the demo and the App Store. Mine didn't.

I'm Jamie Bisset. Before you hire a Head of AI, sign an agency, or bet on a guru who has never shipped, talk to someone who has. I take AI products from idea to production, two to three days a week, with a team behind me that builds at scale. Australia and New Zealand.

Models are brilliant at understanding.

They read context, explain trade-offs, hold a conversation. That part was never the problem.

And unreliable at arithmetic.

Ask one to re-portion a week of meals to the gram and it will do it beautifully, differently, every single time.

So I decide where the model stops.

Plans, macros and money run on code that is right every time. The model interprets, explains and asks before it acts. Drawing that line is the whole job.

Proof, from the product I shipped alone

0hand-curated meal templates
under0sto plan a full week, zero model cost
0native tools in the coach
0%+less coach cost on the same traffic
0languages
0person, first line of code to store review

Fractional Head of AI, or CTO

Three ways I work inside your company.

From a straight answer before you sign, to running the build from idea to the store. Two to three days a week, async by default, Australian Eastern time. Each one has been done for real, not on slides.

  • Take it from idea to production.

    You have the idea, the budget, and nobody who has shipped. I scope it, architect it, run the build, and take it through store review. Product direction and project management are the job, not a side of it: I have done it alone on Meal Engine and with a team on an app that passed a hundred thousand downloads.

  • Read what you have, and who you are about to hire.

    An agency proposal, a prototype, a shortlist of AI candidates. I read the architecture and the code line by line and tell you what is real, what will cost you in a year, and who you actually need. I have directed an outside engineering team for three years and caught what they missed, including a sign-in that would have let anyone log in as anyone.

  • Own the AI direction without a full-time hire.

    Choose the models, decide where the model stops and code starts, set the guardrails, ship agents that see real use in the first month, measure, keep it cheap. The coach in Meal Engine has about eighty tools and has never surprised a customer, and the last prompt-cache change I made cut its cost by more than ninety percent on identical traffic.

Capacity

One person designs it. A team builds it.

Meal Engine was built by one person because it had to be. Your build doesn't. I bring the infrastructure to deliver at scale: architecture and product direction from me, hands from an engineering team I have already shipped with, on an app with over a hundred thousand downloads. I run the build end to end, scope, sprints, review and release, so you get a fractional lead and a delivery capability in one engagement, without hiring either.

The proof

Built alone. Live in both stores. Rated 5.0.

Meal Engine is an AI nutrition coach that builds someone's week, then adjusts it as their days change. It is here as evidence, not as the pitch: every part of it, from the first line of code to the App Store review, was one person.

It listens.

Text, voice, a photo of the plate or a barcode. Seven tiers of lookup run before a model is ever asked, so most logs resolve in milliseconds and the model is the last resort, not the first call.

It plans on code.

Two thousand curated templates, portioned to the gram by a deterministic engine that snaps eggs to whole eggs and bread to slices. A full week in under two seconds, at zero model cost, right every time.

A day's meal plan in Meal Engine with macros and meal cards

It asks first.

About eighty tools. Reads run on their own. Anything that changes a plan, a target or a supplement proposes, waits for a yes, then acts. Every action is logged, so nothing it does is a surprise.

The Engine coach reviewing a week in chat
App Store Google Play 5.0 out of 5 on the App Store. Seven currencies, six languages.
  • "I really like how you can swap or add foods and it just recalculates everything."
    App Store review
  • "Very user friendly, informative, flexible, well rounded food app."
    App Store review
  • "After using MyFitnessPal for years I'd finally had enough, then went on a mission."
    App Store review

How I think

Six decisions that made it real.

Each one exists because the obvious approach failed first. Read them as the judgment you would be hiring.

  • Plans run on code, not on the model.

    The models were good at explaining trade-offs and bad at fast, exact arithmetic across a week of meals. So a deterministic layer builds and re-portions every plan from a library of 2,394 curated templates, and the model interprets, explains and guides. A full week in under two seconds, at zero model cost, and the numbers are right.

  • Only true misses reach a model.

    Logging every food through an LLM was slow and expensive. Text, voice, photo and barcode now flow through one seven-tier resolver: the person's own history, their custom foods, saved meals, a verified nutrition database, and only then a model. Most logs resolve in milliseconds.

  • The coach asks before it acts.

    An agent with write access to someone's plan needs rules. Reads run on their own. Anything that changes a plan, a target or a supplement proposes first, waits for consent, then executes, and every action is audit-logged. People trust it with changes because it never surprises them.

  • Cache the part that never changes.

    Coach cost rose with usage because the prompt's shared knowledge sat below each user's name and date, so no two users ever shared a cache entry. I split the prompt into a static block identical for everyone and a small per-user block. Same traffic, more than 90% less spend, verified in production.

  • No single provider.

    A billing lapse at one provider and a drained key at another each took a feature down. Every call now routes per turn across Anthropic, OpenAI and Google with a fallback chain chosen by task. An outage degrades a feature instead of removing it.

  • Cap what one person can cost.

    A subscriber could chat their way past their subscription price. Each user has a monthly spend ceiling on the coach, and only the coach. Logging a meal is never blocked, because that is the thing they pay for. Margin protected, core use never gated.

Demonstration

This is not me. It's the AI version of me.

Made in an afternoon with the same tools I ship with. My face, my voice, my words. If you're wondering whether I can make this work inside your company, you're looking at the answer.

Jamie Bisset Rendering. Back within the day.

Before Meal Engine

One brain, two apps. And the one that's waiting.

Lift Engine

Three years as product lead on LIFTit, the training app for Stephanie Sanzo's three-million-follower audience, built by an outside agency I direct. Over 100,000 downloads and close to a thousand ratings across both stores. I decide what gets built, review what comes back, and catch what was missed: on one pass I found a sign-in that verified a token's signature but never checked which app it was for. Fixed in both API versions.

It's becoming Lift Engine, and it now runs on Meal Engine's nutrition brain through three server-to-server services, so a fix to the calculation lands in both apps at once.

GymVid

A computer-vision app that analyses lifting form from video. Product lead, with the same agency. Paused by agreement while the two apps above take the oxygen. The IP is intact and waiting.

Live

Ask it anything about my work.

Ask how I would approach your build, what a decision above actually changed, or what I am not good at. The agent is grounded only in what is on this page. It can't see revenue, it can't make things up, and it stops when today's budget is spent. The same three rules the Meal Engine coach lives by.

Ask me how Jamie would approach something you're building, what a decision above actually changed, or what he's not good at.

Today's budget: checking

Meta

How this site was built.

One day. Claude Code wrote most of the code from my direction. Higgsfield generated the sequence you scrolled through and the video of me. The chat above runs on a Cloudflare function with a daily cap, the same pattern as the product. No framework, no build step: one static page and one function. I'm telling you this because the how is the point.

Start here

Three days. Free. Before you sign, not after.

  1. Day 1

    A call.

    You tell me what you're building, what you've already got, and who you're about to hire.

  2. Day 2

    I read it.

    Code, architecture, the proposal on your desk, or just the idea. Alone, properly, the way I'd review my own.

  3. Day 3

    A straight answer.

    What it will take, who you actually need, and whether that's me. Yours to keep, whatever you decide.

If it's a fit, we start in October: a build I run from idea to the store, or a seat inside your company two to three days a week, for as long as the work needs. If it isn't, you've spent three hours and gained a plan.