didodot.

Drawing

DDT-001

Sheet

01 of 05

Status

Issued for use

Location

Sydney, AU

AI implementation into business

design develop deploy didodot.

AI working inside the business, not sitting in a licence nobody opens. The workflows mapped, agents carrying the small repeating jobs that eat your team's week, your people trained so it still holds after I leave, and the production systems underneath when the job needs more than a workflow. One person owns all of it, architecture through to handover. Not templates. Not Zapier.

Start with a diagnosticSee the work
85-table production databaseLive Stripe, real money movingAI scanning pipeline shipped

The repeating work your team does every week is the work AI should take.

Most businesses adopt AI by handing out licences and hoping. That gets you two enthusiastic people and a lot of shelfware. This is the other version: your workflows mapped, agents wired into the tools you already run, guardrails so nothing runs away, and your people trained on their own work rather than a slide deck. What it buys you is the small repeating jobs off their desks, and a setup a new starter inherits instead of rebuilds.

  • 01

    Workflow Audit

    You get a written plan ranked by payback, not a list of AI ideas. It comes from mapping how your team actually works: where the hours go, which processes repeat, and which ones are worth automating first.

  • 02

    Environment Setup

    Your team opens a laptop and it is already set up: instructions written for your business, agents that know their branch, and live connections into the tools you already run. Permissions and spend controls configured, so nothing runs away while you are not watching.

  • 03

    Team Training

    Sessions run on your own work, not a generic slide deck. Engineers, ops, and the people who do not think of themselves as technical each get the version that applies to their job, so nobody sits through an hour that was not for them.

  • 04

    Standards and Guardrails

    The rules that stop it drifting once I am gone. What gets reviewed, what an agent is never allowed to send on its own, and how a new starter picks the setup up on day one instead of rebuilding it.

Built for teams of five to 150. Delivered remotely across Australia, or on-site in Sydney.

The Board

Your org chart, with an agent under every branch and a line it cannot cross.

Five layers are always there, whatever size you are. Two more exist only where somebody already does that job, so the model fits a sole trader and a hundred and fifty person company without becoming two different products.

01CEOthe owner's chair
02Brancha function you already run
03Agentone per branch
04Skillstrained procedures
05Connectorswired to that branch only

The human line. The agent sits outside it, and nothing it produces reaches a customer without a person approving it first.

Present only where someone already does that job

06Arm Leadruns several branches
07Branch Managerruns one or two

Enforced in the wiring, not on the honour system.

See how the whole board works

The control room

AI that sits next to you while you work, not in another tab you have to remember to open.

A small window on the side of your screen. One panel is what needs you today. The other four are the parts of your business you actually run, each with an agent behind it that only touches that part. You type what you want in plain words, watch the real steps, and nothing goes out the door without you saying so. It is in build now, and this is the drawing.

Now

8 need you
Needs you
1
Wrap-up document
Owed to a client. Four days over.
LATE⌘4
2
The supplier (example)
Draft ready · August pricing
YOU⌘2
3
The client (example)
Draft ready · this week's timing
YOU⌘2
4
Website enquiry (example)
New. Asks about a systems review.
YOU⌘2
5
Site walk invite
Goes to two people outside the business. Waiting on your say so.
YOU⌘2
6
LinkedIn post, drafted
Written by the Make agent. Waiting on your say so.
YOU⌘4
7
Two open questions
Only you can answer these.
YOU
8
Invoice 001
Due in six days.
DUE

Fig. 1 · Interface study, not a working build. The rail is live, hover it.

The widget follows the system theme: the same window, lit for light mode and for dark. The demo opens as you scroll to it, and the dot opens under your cursor, the way the real one does. The real thing appears the instant you press the key, with no animation at all, because you will summon it fifty times a day and anything that makes you wait gets uninstalled.

  • 01

    One window, one key

    Pinned to the side of the screen, out of the way until you press one key, and gone again with the same key. It sits over whatever you are working in, so the AI is in the job rather than in a licence nobody opens.

  • 02

    A panel per branch, an agent behind each

    Slot 01 never changes: what needs you today, ranked, with what is blocking each one. The other four are named for the jobs your business actually does, so the same tool arrives looking different in every business.

  • 03

    Nothing outward sends itself

    An agent can reach its branch's systems and nothing else, and anything that leaves the building comes back as a draft for you to approve. That is wiring, not policy, and it does not move.

  • 04

    You watch the real steps

    Every step named, counted and timed as it happens, so you always know where a job is up to. What proves an agent is working is a number changing, not a spinner spinning.

In build. No dates on purpose: each phase lands once its gate is proven.

See the build plan

When a workflow is not enough, this is what gets built.

These are the six shapes the build work takes. Yours will not match one of them exactly, which is what the diagnostic is for: the scope comes from your systems, not from this list.

ItemSystemDescription
01AI PipelinesWork a person currently does by reading, checking and typing, done by a machine instead. Photos read, documents extracted, facts verified against outside sources, results scored. Built to keep running under load, not to demo well.
02Payment InfrastructureTaking money without inheriting a bookkeeping problem six months later. Live Stripe, webhooks that cannot double-charge, ledgers that reconcile, affiliate attribution and payouts. The kind that holds when the money is real.
03Assessment & Scoring EnginesTurning what a customer tells you into an answer you can stand behind. Quizzes, scoring models and personalised recommendations, with the calculation documented and repeatable, so you can show anyone how a result was reached.
04User & Practitioner EcosystemsMore than one kind of user, each seeing only what they should. Staff, customers, practitioners and their clients, with the access rules built into the database rather than the interface. That is the difference between private and looks private.
05Database ArchitectureThe part nobody sees and everything else depends on. Schema design, access rules hardened, security reviewed, queries kept fast as the data grows. Get this wrong and every feature above it inherits the problem.
06System Integration & AutomationYour existing tools talking to each other, with judgement in between. For the workflows where the decision is too specific for a rule to cover and Zapier gives up. Nothing that already works gets replaced.

Every build here is fixed price, scoped in the diagnostic before it starts.

Three steps. No surprises.

  1. Step 01

    Paid Diagnostic

    You walk away with a written plan: itemised scope, a fixed-price quote, and the real shape of the problem written down. Getting there means a scoping session and an audit across your systems and how your team actually works. That audit leaves a record of how the business really runs, and it is yours to keep: your team can point their AI at it from day one, and if you continue it is the same record I build from. You pay for the diagnostic whether or not you proceed, which protects you from scope surprises and me from quoting blind.

    AUD $2,500 · paid whether or not you proceed

  2. Step 02

    Fixed-Price Delivery

    The price is set before anything starts and it does not move. No hourly tracking, no invoice that grows. Whether it is a system built and verified against your live data or your team set up and trained, you agreed the scope before I began.

  3. Step 03

    Ongoing or Done

    At handover you get documentation, a system tested on your real data, and everything you need to run it without me. If you want me on the next phase, that is available. If you want to take it and go, that is the normal outcome, not a failed relationship.

Systems record

One build, start to finish, by one person. This is the one to judge me on.

ClientBridge TheoryScopeFull platform, from schema to launchStatusLive, externally security audited

A clinical health assessment platform built from scratch to production.

bridgetheory.health needed a complete platform: a chemical exposure scoring engine, an AI product scanning pipeline, a live payment system, a practitioner ecosystem, and a security architecture that could pass an external security audit. It needed to handle real money, real patient data, and real practitioners from day one.

  • Verified85Database tables
  • Verified8Webhook event types
  • Verified19Test categories
  • Live$20,000Commercial build
SystemWhat shipped
Scanning pipelinePhoto capture, OCR, ingredient extraction, web verification and chemical flagging, on an async queue with trace logging
PaymentsLive Stripe with 8 webhook event types, idempotency and 5-minute replay protection
Database85 tables, RLS hardened, externally security audited
Test coverage19 categories end to end across auth, payments, quiz, scoring and practitioner flows
RevScopeVerified
A85-table schema, RLS hardenedAudited
BAI scanning pipeline on async queueLive
CStripe, 8 webhook types, replay protectedReal money
D19-category end-to-end smoke suitePassing

Outcome: a $20,000 commercial build, launch-ready and externally security-audited, verified on live infrastructure with real paying customers.

Externally security audited
“We'd attempted to create the website ourselves but it was simply too complex. We were getting bogged down on bugs that Rhys handled quickly, which was a massive weight off of our shoulders. As development progressed, I was surprised with the value add from Rhys. Our system didn't have plans for OCR, which has turned out to be a massive improvement in helping us get as close to the truth as possible and helping people in pain demystify environmental factors. I would recommend Rhys' services to anyone who is doing intricate software development. He's passionate about task completion and adds value in places you wouldn't expect.”
Lachlan Carrucan, Co-founder, Bridge Theory

References available: Peter Werle and Lachlan Carrucan, Bridge Theory founders.

Start with a diagnostic

One person. Full ownership. No handoffs.

I am Rhys. I am based in Sydney, I run didodot on my own, and I am the only person you will deal with from the first call to the handover.

I do not write code line by line. I decide the architecture, run AI build tools to execute it, and check every output against live data before it counts as done. didodot is open about working that way. It is why one person can carry a build that would normally need a team, and why verification, not typing, is where the hours go.

You get one person who owns the whole problem: architecture, build, testing, security, handover. Nobody to chase, and nothing lost between two contractors.

didodot · ABN 80 144 081 170 · Sydney, Australia

  • Supabase + PostgreSQL
  • Stripe live mode
  • AI-native build methods

How the work runs

  • ArchitectureDecided by me, before any build starts
  • BuildAI build tools, orchestrated and reviewed
  • VerificationEvery output checked against live data
  • HandoverDocumentation, tests, one owner end to end

Tell me what the business is dealing with.

Everything starts with a diagnostic. You get a written plan, an itemised scope and a fixed-price quote before you commit to a build. If the honest answer is that you do not need one, I will tell you that.

  • How many people you have, and what the business does
  • What you want implemented, in your own words
  • What is breaking or missing right now
  • Any timing or budget you already have in mind

The diagnostic is AUD $2,500, scoped and booked after we talk. Sending this costs nothing.

Your name, email and message go to our form provider and then to our inbox. Nothing else is collected and nothing is tracked. Privacy policy

Response within 24 hours · rhys@didodot.com · Sydney, Australia · ABN 80 144 081 170

Your details go to didodot only, and only so I can reply.