Your AI delivery manager In private development · Early access from early 2027

Give Declan the outcome. Get back verified software.

Coding agents write the code. Declan runs the delivery.

Describe what you want built or changed. Declan plans it, hands the work to AI coding agents, has each result checked separately and tracks spending against a ceiling you set. It is designed to run above the coding agents you already use, starting with Claude.

You stop briefing, chasing and re-checking. You get working software in your repository, with a record of what passed and what it cost.

Request early access See how a delivery ends

Illustrative example

Delivery DL-0107

  1. Owner · 09:14

    Migrate checkout to Payment Intents. Keep the webhook contract. Under $300 of AI spend, production-ready by Friday.

  2. Declan · 09:16

    Objective recorded as stated. Context read: the checkout repository, three open tickets and the webhook documentation. Proposed plan: four packages for engineering and testing coding agents, under a $300 ceiling. One decision is yours before work starts.

    PLAN · 4 PACKAGES · CEILING $300

  3. Reserved for you

    Should the legacy Charges endpoint stay callable during the migration?

    Service structure and test strategy are delegated to Declan. Whether existing integrations can keep calling Charges until cut-over is yours to decide. Work starts when you answer.

    Keep Charges callable Retire Charges now Ask a question first

02 · The delivery problem

Human judgement is valuable. Human orchestration is waste.

AI tools now write a lot of the code. Someone still has to run the delivery: brief each tool, check what came back, chase what is stuck and decide what counts as finished. That work lands on a founder or the most senior engineer, and it grows with everything the AI produces.

  • Context

    Each AI tool starts every session without the history. The objective and the decisions live in one person's head.

  • Checking

    “It passed” usually means the thing that built it said so.

  • Follow-up

    Someone has to notice what stalled, what drifted from the brief and what still needs a decision.

  • Cost

    Spend shows up per tool and per token, never per delivered outcome.

03 · How a delivery ends

Decisions in the thread. Progress without asking. Evidence at the end.

Declan is designed to work like a member of your team, in its own workspace and in the tools your team already uses. Here is how the delivery above continues.

The delivery line One line from the owner, through the owner's decisions and Declan, to AI coding agents, a remediation loop and a separate verifier. It ends either verified or unresolved. A dotted evidence trail runs beneath it to the outcome. ENG ENG TEST REMEDIATION OR OWNER YOUR DECISIONS DECLAN CODING AGENTS SEPARATE VERIFIER VERIFIED UNRESOLVED EVIDENCE TRAIL The delivery line One line from the owner at the top, through the owner's decisions and Declan, to AI coding agents, a remediation loop and a separate verifier. It ends either verified or unresolved. ENG ENG TEST OR OWNER YOUR DECISIONS DECLAN CODING AGENTS REMEDIATION SEPARATE VERIFIER VERIFIED UNRESOLVED

Illustrative example

Delivery DL-0107, continued

  1. 09:31 · Keep Charges callable · decided by Owner

  2. Declan · 11:52Verified

    Package 2 of 4 verified: webhook handler. A separate verifier passed 18 of 18 checks. Package 3 is in progress. Spend $112 of $300.

  3. Eng lead · 12:05

    @Declan what changed in the webhook handler?

  4. Declan · 12:05

    Signature verification moved into middleware. The payload contract is unchanged and six contract tests cover it. The diff is in pull request #482.

  5. Declan · 15:40Verified

    4 of 4 packages verified by a separate verifier. Pull request #482 is ready for review with the record attached. Three tickets updated. A preview of the branch is running. Spend $241 of the $300 ceiling.

    SEALED · DL-0107 · 8f3a2c…e91d

Your part in this example

  • 1 request
  • 1 decision
  • 1 pull request to review

Declan did the planning, briefing, chasing, checking and reporting.

What just happened

One objective, held throughout

Your request is written down once, in your words, and every check is made against it.

Only your decisions came to you

Declan said up front what it would decide and asked you one question, with the answers as the options.

Checked by something that did not build it

Each package was checked against your objective. Anything that does not pass is fixed within a set number of attempts, or marked unresolved and handed back to you.

Delivered with the evidence

A pull request, updated tickets, a working preview and a sealed record, back in the conversation where the work began.

04 · Build · Deliver

Start from an idea, or from software you already run.

Build and Deliver are two ways into the same managed delivery: the same planning, checking, budget and record.

From an idea

Build with Declan

From an idea to working software.

For founders and businesses creating something new, without an engineering team to manage. Describe your idea in plain words and set a ceiling. Declan plans it with you, builds it in checked steps and shows you each one working, so you can ask for changes before you accept it.

Starts from
Your idea, in your words
You see
Each checked step, working
You get
Working software, in your repository

For example

  • A customer portal for a services business
  • An internal tool to replace a tangle of spreadsheets
  • The first version of a new product
  • Online booking and payments for a clinic

Founders, operators and businesses without an engineering team.

Start with Build

From your repository

Deliver with Declan

Changes, fixes, migrations and releases on software you already run.

For teams with software in production and AI coding agents already in use. Hand Declan an objective against your repository. It reads the code and its history, runs the work through AI coding agents and checks each piece separately, so your senior people review outcomes instead of running every handoff.

Starts from
Your repository and an objective
You review
Pull requests with the evidence attached
You get
Verified changes, fixes and releases

For example

  • Migrate payments without disrupting existing customers
  • Fix 14 checkout issues and prove each one is fixed
  • Get enterprise-ready with SSO and the audit findings
  • Get v2.4 release-ready by Friday, within budget

Engineering leads, technical founders and teams already using AI coding tools.

Start with Deliver

Or all four, as one objective

A coding agent works on individual changes. Declan manages the delivery around them.

Illustrative example

Owner · Objective

Enterprise SSO, the payments migration, the 14 checkout issues and the security audit findings. Keep backward compatibility, stay under $1,500 of AI spend and get v2.4 production-ready by Friday.

Declan

Plans 11 packages for coding agents

  1. Enterprise SSO 3 packages

  2. Audit findings 2 packages · after SSO

  3. Payments migration 4 packages

  4. 14 checkout issues 2 packages

v2.4 · Release-ready

Checked separately
11 of 11
AI spend
$1,214 of $1,500
Brought to you
2 decisions

05 · Verified, not just finished

Verified means a separate check passed.

A separate verifier checks the work against the objective you accepted. If it passes, it is verified. If it does not, Declan fixes it within a set number of attempts and checks again. If it still does not pass, it is marked unresolved, the record shows why, and the decision comes back to you.

The check runs your tests and the acceptance criteria written into the plan, then a separate verifier session reviews the result against your objective. It covers what those tests and criteria describe. It is not a security audit, so pull requests still come to you for review.

Every outcome carries its record: who produced it, who checked it, what it cost and when it was sealed so that it cannot be changed afterwards.

The verifier is always a separate session from the one that did the work, enforced in the workflow. Today it may run on the same AI provider as the builder.

Illustrative example record

Package DL-0107-2 · Webhook handler

Produced by ENG-1, checked by automated tests, then verified by VER-1 as a separate step. Record sealed; no further edits.

PRODUCEDENG-1 · 10:42:18
CHECKSautomated 17 / 18 · 10:58:04
FOUNDcontract test 14: header renamed · 11:02:31 · VER-1
REMEDIATEDattempt 1 of 3 · 11:21:47 · ENG-1
RE-VERIFIED18 / 18 checks pass · 11:49:10 · VER-1
CLOSEDsealed 11:52:03 · AI spend $38.60

SEALED · 4be91c…07ad

06 · You keep control

Your decisions, your ceiling, your preview.

Before work starts, Declan says what it will decide and what it will bring to you. Spending is tracked against a ceiling you set. And nothing is accepted on a description alone: you see it working first.

Only the decisions that are yours

Declan asks one question at a time, in plain words, with the answers as the options. Everything else keeps moving.

Reserved for you

Export decision history: should archived decisions be included?

Format is delegated to Declan. Whether archived decisions appear is yours to decide. The export waits for your answer.

Include archived Exclude archived Ask a question first

A spending ceiling you set

Every delivery has a ceiling. Declan records what each package costs, reports spend as it goes and does not start another package beyond the ceiling without asking you. A package already running finishes, so the final figure can land slightly over.

Attention

Spend is at $36.20 of a $40.00 ceiling. Declan will not start the next package until you raise the ceiling or stop.

CEILING $40.00SPENT $36.20REMAINING $3.80

Seen before it is accepted

Each verified package comes with a running preview of the branch. Use it, then ask for changes in the same conversation.

PREVIEW · DL-0107 · 4 OF 4

Verified

Branch checkout-payment-intents, running.

Open preview Request a change

Interface examples on this page are illustrative.

07 · Your tools

Keep your coding agents. Add the manager.

Declan does not replace your coding agents or the tools your team already runs. It is designed to manage them: each coding agent gets a scoped package of work, Declan checks the result separately, tracks the spend against your ceiling and keeps the record. Code stays in your repository and conversations stay where your team already talks.

Coding agent

Claude Demonstrated

Does the building, and runs the separate verifier session, in Declan's own development to date.

Coding agents

Codex and others Planned

Declan is designed to manage several coding agents rather than one.

Repository

GitHub In development

Code, history and branches, with pull requests returned carrying the record.

Team conversation

Slack · Microsoft Teams Planned

Objectives handed over, questions answered and progress followed in the thread.

Work tracking

Jira Planned

Issues linked to the delivery and updated as packages are verified.

Demonstrated means used in Declan's own development. Planned integrations are built in the order early-access teams need them.

08 · Early access

Early access opens in early 2027.

Declan is in private development and is being built and tested on real software. A small number of founders and engineering teams will join first.

What early access involves

  • Real delivery objectives on your own software.
  • Integrations set up around the tools your team already uses.
  • A measured record of every intervention: what Declan did, what a person did and why.

Who is building Declan

Declan is being built in Australia by Brett, who previously founded ScreenlyyID, an identity verification platform. While building a risk-decisioning platform with AI tools, he found he was spending more time running the work than deciding it: copying instructions between tools, passing one AI’s review to another and keeping track of which version of the plan was current. Declan exists to take that work away. Every request is read personally.

The longer aim: a technical team member that stays with your product, holds its context and manages its delivery, with the coordination taken out and the judgement kept in.

What would you hand to Declan first?

Which describes you

In your own words. One paragraph is enough.

Where does your team work? (optional)

Used only to reply to you. Read the privacy notice.