AI audit · 1 week

Not sure which kind of build you need? Start here. It’s a fixed price, and sometimes the answer is don’t build.

We read the code that exists and the data and workflows around it, then rank what’s worth building.

Service 04 / 04dynode.ai

Length
1 week
Price
Fixed, before you commit
You keep
Process map, ranking, reasoning
If it’s worth building
A one-week blueprint follows
If it isn’t
You stop there

Who it’s for

Every build we take on starts here, so you know what you’re paying for before you pay for it.

A good call when

  • You’re not sure whether you need a prototype taken to production, a new platform or AI in an existing workflow.
  • You have a list of AI ideas and no way to tell which one would pay for itself.
  • You have code, data or a workflow that someone should read before anyone quotes a build.
  • You’d rather learn it isn’t worth it in one week than after a build.

Not the right fit when

  • You want an hourly team writing code tomorrow. Every engagement starts with the audit, so the price is set before the code.
  • You’re still validating the idea. Keep building with the AI tools until someone depends on it.

Already know what you need? See the three kinds of build

What’s included

One week, one fixed price, and findings that are yours whatever you decide next.

  1. The code that exists

    Whatever is already built, read by the engineers who would build the next part.

  2. Your data

    Where it lives, how it flows, and what would be sent to a model provider.

  3. The workflows around it

    How the work actually runs today, mapped step by step.

  4. The process map

    Yours to keep.

  5. The opportunity ranking

    What’s worth building, in order, and what isn’t.

  6. The reasoning

    Why each item ranks where it does, written down.

audit / outcomeschematic
Audit1 week · fixed price

Worth building

Blueprint, 1 week

Build price fixed in writing

Then build, or walk away with it

Not worth it

You stop there

You’ve spent an audit, not a build

You keep the map, ranking and reasoning

What happens after the audit week. Both ways, the findings are yours.

How it runs

Every build we take on starts with this week. If the ranking says build, the blueprint follows the next week.

  1. 1 week

    Audit

    We read the code that exists and the data and workflows around it, then rank what’s worth building. If nothing on the list is worth it, we say so, and you keep the process map, the ranking and the reasoning.

  2. 1 week

    Blueprint

    We write down how the system will be built, what’s in scope and what ships in which week, then put a fixed price on the build. The blueprint is yours to keep, whether or not you build with us.

  3. 4–12 weeks

    Build

    A working build, demoed to you every week, running on something you can click. 4–8 weeks to take a prototype to production, 4–12 for a new build.

  4. Ongoing

    Run

    Two ways to go. We run it, with hosting, monitoring and support on a monthly retainer. Or we hand it over completely: the code, the documentation, the eval setup and access to everything. It’s a choice, not a dependency we engineer in.

One week in, you know what’s worth building. Then you go ahead with the blueprint, or stop with the findings.

  • Fixed price, before you commit
  • You keep the findings either way
  • No obligation to build with us

FAQ

If your question isn’t here, ask it when you write. We reply within one business day.

What is the AI audit?

A one-week, fixed-price review of your workflows, data and existing code that ranks what is worth building. We read the code that exists and the data and workflows around it. Sometimes the recommendation is not to build, and you keep the process map, the ranking and the reasoning either way.

How is the price set?

We price the audit as a fixed fee before you commit. If it shows the build isn’t worth doing, you stop there and keep the findings. Otherwise a one-week blueprint follows, and at the end of it, two weeks in, the build price is fixed in writing before we write code.

What happens if the audit says we shouldn’t build anything?

Then that’s the deliverable, and it’s the cheapest possible outcome for you. You keep the process map, the opportunity ranking and the reasoning, and you’ve spent the price of an audit instead of the price of a build that wouldn’t have paid for itself. Better to learn that in one week than after a build.

Do we have to build with you after the audit?

No. If the audit shows the build isn’t worth doing, you stop there and keep the findings. If it is, a one-week blueprint follows with the architecture, scope, milestones and a fixed build price. The blueprint is yours to keep, whether or not you build with us.

Who does the audit?

Senior engineers, led by the person who would design your system. They read the code, the data and the workflows themselves, and they’re the people you talk to, from the first call to handover if you go ahead.

Where does our data go?

Into your own accounts and infrastructure wherever possible, deployed in the cloud region your customers or regulators require. We work with least-privilege access, review the data flows during the audit, and document exactly what is sent to which model provider and why. The model stays your choice: we work with OpenAI, Anthropic and open-weight models.

A few lines is enough. We reply within one business day.

Or write directly:hello@dynode.ai+1 332-456-0669