Skip to content

AI automation for UK architecture + interior practices

Your software runs your projects.Nothing runs the gaps.

AutoArch builds the compliance and coordination layer between the tools your practice already owns — planning deadlines, stage-gate invoicing, revision records, contract administration.

Watch a workflow run

Built by a team that has served architecture and interior practices for eight years.

02The architect's reality

SECTION A–A · 1:100

You became an architect to design.

So why does running your practice feel like this?

Design isn’t the problem.

Everything around design is.

03Solved and unsolved

Your practice already runs on software. It still runs on you.

Every practice we speak to owns a full stack. None of it covers the work that carries the risk — the deadlines, the evidence, the money that follows a signature.

Your software already does this

  • File storage
  • Task boards
  • Timesheets
  • Invoicing
  • CAD
  • Calendars
  • Video calls
  • Document signing

You’ve already bought this. We’re not selling it to you again.

Nobody’s software does this

  • Tracking a determination date across eleven live applications
  • Proving which drawing revision the client actually signed off
  • Linking RIBA stage sign-off to the invoice that should follow it
  • Assembling a golden thread record that survives scrutiny
  • Chasing a consultant RFI that has gone quiet for nine days
  • Serving a pay-less notice inside the statutory window
  • Keeping a decision register from a site meeting that nobody minuted
  • Logging practice CPD hours before the deadline panic

This is the layer AutoArch builds.

04The invisible layer

Meet the invisible layer behind your practice.

AutoArch connects the tools your studio already uses and builds intelligent workflows between them. Your team keeps designing. AutoArch handles what happens next.

Drawing AA-SVC-04

OUTLOOKTEAMSFORMSAUTOARCHNODE 00 · X 0400 Y 0176CRMPROJECT MANAGEMENTDRIVECALENDARACCOUNTINGAISOURCE → DESTINATIONAA-SVC-04 · INTEGRATION LAYERNTS
DRAWING
AA-SVC-04
LAYER
INTEGRATION
REV
03

Sources on the left, systems of record on the right. AutoArch is the layer in between.

05The RIBA Plan of Work, run

Stage 0 to stage 7, without the gaps.

AutoArch runs the work between the stages — the deadlines, the records and the money that should follow a signature but usually doesn’t.

Scroll ↓

RIBA STAGE 0–1

Strategic Definition & Brief

Trigger

ENQUIRY · 09:14

Rear extension and loft conversion — 5-bed Victorian terrace, Hackney.

AutoArch fires

Sequence

  1. 01Captures the enquiry
  2. 02Creates the contact record
  3. 03Identifies typology and constraints
  4. 04Qualifies budget against scope
  5. 05Assigns to an associate
  6. 06Sends a personalised response
  7. 07Books the feasibility call

Enquiry to booked feasibility · no one touched it

RIBA STAGE 2

Concept Design

Trigger

APPOINTMENT · CONFIRMED

Client appointed. Stage 2 opens.

AutoArch fires

Sequence

  1. 01Creates the client folder and structure
  2. 02Issues the letter of appointment
  3. 03Verifies the PII certificate
  4. 04Requests consultant appointments
  5. 05Opens the pre-application record
  6. 06Sets the stage fee drawdown

Project set up before the first sketch

RIBA STAGE 3

Spatial Coordination

Trigger

SUBMISSION · VALIDATED

Planning application validated by the council.

AutoArch fires

Sequence

  1. 01Arms the determination clock
  2. 02Opens the RFI register
  3. 03Chases consultants that go quiet
  4. 04Logs consultee comments as published
  5. 05Escalates before the date, not after

The determination date is now something watching you, not something you remember

RIBA STAGE 4

Technical Design

Trigger

SHAREPOINT · 16:02

Kitchen_GFC_RevC.pdf lands in the folder.

AutoArch fires

Sequence

  1. 01Detects the revision
  2. 02Supersedes and archives Rev B
  3. 03Updates the drawing register
  4. 04Assembles the Building Regs pack
  5. 05Tracks conditions discharge
  6. 06Records who approved what, and when

The right drawing, provable eighteen months from now

RIBA STAGE 5

Construction

Trigger

CONTRACT ADMIN

Valuation due. Certificate window opens.

AutoArch fires

Sequence

  1. 01Prepares the interim certificate
  2. 02Flags the payment notice window
  3. 03Issues instructions and logs them
  4. 04Turns site inspections into reports
  5. 05Assigns snagging items to a name

Certificates and notices on the clock, not in someone’s head

RIBA STAGE 6–7

Handover & Use

Trigger

PRACTICAL COMPLETION

Works complete. Handover opens.

AutoArch fires

Sequence

  1. 01Assembles the O&M manual
  2. 02Closes out the golden thread record
  3. 03Issues the final account
  4. 04Files the decision register
  5. 05Archives the project, indexed

The record is finished because it was built as you went

Project brief

AUTO-GENERATED

PROJECT
Rear extension + loft conversion
PROPERTY
Victorian terrace, Hackney · conservation area
AREA
297 m² existing · 61 m² proposed
SCOPE
RIBA Stages 1–6
BUDGET
£280,000–£340,000 construction cost
TARGET
Stage 3 submission by 14/03/2027

06Proposals that build themselves

Stop rebuilding the same proposal for every project.

The brief is already structured. AutoArch drafts the sheet from it, names the file, sends it, and keeps following up until there is an answer.

Fee proposal

AA-PRO-118 · REV 01

CLIENT
M. Ellery
PROJECT
Rear extension + loft conversion, Grade II listed
SCOPE
RIBA Stages 1–6
FEE BASIS
Lump sum per stage
STAGE 1
Preparation & Brief
£2,400
STAGE 2
Concept Design
£6,200
STAGE 3
Spatial Coordination
£7,400
STAGE 4
Technical Design
£9,800
STAGE 5
Construction — CA services
£6,600
STAGE 6
Handover
£1,700
SUBTOTAL
£34,100
VAT
Shown separately at prevailing rate
EXCLUSIONS
Planning fees · Building Control · consultant fees · surveys
TERMS
Monthly in arrears · RIBA Standard Professional Services Contract

DRAWN

AUTOARCH

DATE

AUTO

SHEET

1 / 1

Saved as

Status

  1. SEND
  2. FOLLOW-UP
  3. REMINDER
  4. ACCEPTED

No one had to remember the follow-up. It was already scheduled.

07Project onboarding

One approval. An entire project starts itself.

The moment a proposal is accepted, everything a new project needs already exists — folders, team, template, milestones, schedule.

Trigger

Accepted

The only human decision in this whole sequence.

  1. 01Project created
  2. 02Client folder
  3. 03Team assigned
  4. 04Project template
  5. 05Milestones
  6. 06Client welcome
  7. 07Kickoff meeting
  8. 08Payment schedule

  9. Project live · 0 manual setup steps

08Compliance operations

The three places a practice actually gets caught.

Not generic triggers. The specific, repeated motions where an architecture practice carries risk — evidence, deadlines, and what was decided in a room.

WF-04 — Revision control + evidence trail. 1 human step, 6 automated steps, about 6 hours a month reclaimed.

  1. Step 1. File lands in project folder (SHAREPOINT). Listens on the issued-drawings library
  2. Step 2. Parse drawing number + revision. Reads the title block, not the filename
  3. Step 3. Match against drawing register (REGISTER). Finds the superseded sheet
  4. Step 4. Supersede + archive Rev B. Moves, does not delete
  5. Step 5. Stamp issue sheet + audit line. Who, what, when, to whom
  6. Step 6. Notify the distribution list (TEAMS). Contractor, structural, client
  7. Step 7. Evidence trail entry. Immutable, dated, attributable

Risk points in this workflow:

  • Unrecognised sheet. No register entry. Held, not guessed at — an unrecorded revision can supersede an approved one.

Steps you still do:

  • Confirm the sheet

WF-01 — Statutory deadline tracking. 1 human step, 5 automated steps, about 9 hours a month reclaimed.

  1. Step 1. Application validated (PLANNING PORTAL). Watches every live application
  2. Step 2. Arm the determination clock. Target date recorded against the project
  3. Step 3. Poll for consultee comments. Daily, logged as published
  4. Step 4. Track conditions for discharge. Each condition its own item
  5. Step 5. Determination window closing. Escalates before the date, not after it. This is the point of the whole workflow.
  6. Step 6. Agree extension or push. A judgement call, surfaced early
  7. Step 7. Application register updated. Every live application, one view

Risk points in this workflow:

  • Determination window closing. Escalates before the date, not after it. This is the point of the whole workflow.

Steps you still do:

  • Agree extension or push

WF-10 — Meeting intelligence → decision register. 1 human step, 6 automated steps, about 5 hours a month reclaimed.

  1. Step 1. Site meeting recorded (TEAMS). 43 minutes, four attendees
  2. Step 2. Transcribe + attribute. Who said it, not just what
  3. Step 3. Extract decisions and actions. Separates a decision from a comment
  4. Step 4. Assign to a name and a date. Never to “the team”
  5. Step 5. Flag client changes as variations. Cost consequence surfaced now
  6. Step 6. Decision register entry. Dated, attributable, exportable
  7. Step 7. Minutes issued (OUTLOOK). Within the hour

Risk points in this workflow:

  • Ambiguous decision. Flagged rather than recorded wrongly. A wrong entry in a decision register is worse than a gap.

Steps you still do:

  • Confirm the ambiguous items

Amber marks a statutory deadline or a liability point. Peach marks the only steps a person touches.

09Site coordination

Your office automation shouldn’t stop at the office.

What happens on site is the least structured information a practice handles — and the most expensive to lose.

SITESTUDIOCLIENT
  1. 01Site architect uploads photos
  2. 02AutoArch analyses and organises
  3. 03Site Report #018 generated
  4. 04Issues extracted
  5. 05Tasks assigned
  6. 06Client update generated
  7. 07Dashboard updated

Site Report #018

ISSUES · 3

  • False ceiling correction
  • Electrical point relocation
  • Stone delivery delayed

Site → Studio → ClientWithout 47 Teams messages in between.

10Practice record

You are about to let someone inside your practice.

So here is who you would be dealing with, exactly what happens to your data, and how the first engagement runs — before you give anyone a login.

10.1 — How an engagement runs

Programme · indicative

  1. 01DiscoveryWeek 1

    We map your stages, your stack and where the time actually goes. Output is a written workflow map — yours either way.

  2. 02Workflow 01 builtWeeks 2–3

    One workflow. The one costing you most, scoped to a fixed price before anything starts.

  3. 03Live in your practiceWeek 4

    Running against your real projects, with someone accountable when it matters.

  4. 04Build-outOngoing

    Only if the first one earned it. You decide, one workflow at a time.

One workflow first, scoped to a fixed price. If it does not earn its place, that is where it stops — and you keep the workflow map either way.

10.2 — Who is behind this

Founder

8 years building operations for architecture and interior practices. You deal with the person who builds the thing — not an account manager, not a support queue.

10.3 — Evidence

Founding practices

We have no case studies yet, so we are not going to show you one.

AutoArch is taking on a small number of founding practices at reduced fee for the first build, in exchange for a written account of what actually changed. When there are results, they will appear here named, dated and checkable — or not at all.

No stock logos. No invented numbers.

10.4 — Your data

AA-DAT-001 · REV 01

D.01
Residency
Practice data is stored and processed in the UK or EU. Nothing is moved outside that without your written instruction.
D.02
Model training
Your drawings, correspondence, fee data and client records are never used to train any model — not ours, not a third party’s. There is no exception clause hidden in a policy page.
D.03
Processing agreement
A DPA is available on request and is signed before any practice data is touched, not after.
D.04
Sub-processors
The current list — orchestration host, model provider, mail relay — is published and versioned. You are told before it changes.
D.05
Exit
Your workflows, records and data export on request. Nothing about the arrangement is designed to make leaving difficult.

AA-PRA-000 · PRACTICE RECORD · REV 01 · NTS

Written to be checked. If any line here turns out to be wrong, it is a defect and we fix it.

11The workflow library

Where is it actually hurting?

Fifteen workflows. Pick the one costing you the most this week — that is the one we build first, and the only one you have to commit to.

15 / 15

  • WF-01 — Statutory deadline tracking. 1 human step, 5 automated steps, about 9 hours a month reclaimed.

    1. Step 1. Application validated (PLANNING PORTAL). Watches every live application
    2. Step 2. Arm the determination clock. Target date recorded against the project
    3. Step 3. Poll for consultee comments. Daily, logged as published
    4. Step 4. Track conditions for discharge. Each condition its own item
    5. Step 5. Determination window closing. Escalates before the date, not after it. This is the point of the whole workflow.
    6. Step 6. Agree extension or push. A judgement call, surfaced early
    7. Step 7. Application register updated. Every live application, one view

    Risk points in this workflow:

    • Determination window closing. Escalates before the date, not after it. This is the point of the whole workflow.

    Steps you still do:

    • Agree extension or push

  • WF-02 — Stage-gate invoicing. 1 human step, 4 automated steps, about 7 hours a month reclaimed.

    1. Step 1. RIBA stage signed off (PROJECT)
    2. Step 2. Match stage to the fee schedule
    3. Step 3. Draft the invoice (XERO)
    4. Step 4. Attach the stage evidence
    5. Step 5. Invoice issued + logged (XERO)

    Risk points in this workflow:

    • Drawdown not raised. A signed-off stage with no invoice behind it is unbilled work ageing quietly.

    Steps you still do:

    • Approve and release

  • WF-03 — Contract administration. 1 human step, 4 automated steps, about 8 hours a month reclaimed.

    1. Step 1. Valuation date reached (CONTRACT)
    2. Step 2. Assemble the valuation
    3. Step 3. Draft the interim certificate
    4. Step 4. Open the notice window
    5. Step 5. Certificate + notice issued (OUTLOOK)

    Risk points in this workflow:

    • Notice window closing. A payment or pay-less notice served late has consequences the practice carries, not the client.

    Steps you still do:

    • Certify

  • WF-04 — Revision control + evidence trail. 1 human step, 6 automated steps, about 6 hours a month reclaimed.

    1. Step 1. File lands in project folder (SHAREPOINT). Listens on the issued-drawings library
    2. Step 2. Parse drawing number + revision. Reads the title block, not the filename
    3. Step 3. Match against drawing register (REGISTER). Finds the superseded sheet
    4. Step 4. Supersede + archive Rev B. Moves, does not delete
    5. Step 5. Stamp issue sheet + audit line. Who, what, when, to whom
    6. Step 6. Notify the distribution list (TEAMS). Contractor, structural, client
    7. Step 7. Evidence trail entry. Immutable, dated, attributable

    Risk points in this workflow:

    • Unrecognised sheet. No register entry. Held, not guessed at — an unrecorded revision can supersede an approved one.

    Steps you still do:

    • Confirm the sheet

  • WF-05 — Client approval register. 1 human step, 4 automated steps, about 4 hours a month reclaimed.

    1. Step 1. Approval requested (OUTLOOK)
    2. Step 2. Record what was sent, exactly
    3. Step 3. Remind on schedule
    4. Step 4. Capture the response verbatim
    5. Step 5. Approval register entry (REGISTER)

    Risk points in this workflow:

    • Approval still open. An unanswered approval blocks a stage and nobody is counting the days.

    Steps you still do:

    • Chase or escalate

  • WF-06 — Consultant RFI chasing. 1 human step, 4 automated steps, about 5 hours a month reclaimed.

    1. Step 1. RFI raised (REGISTER)
    2. Step 2. Log against the project
    3. Step 3. Set the response date
    4. Step 4. Chase, politely, on a schedule (OUTLOOK)
    5. Step 5. RFI register updated (REGISTER)

    Risk points in this workflow:

    • RFI gone quiet. An unanswered RFI stops being a coordination problem and starts being a programme problem.

    Steps you still do:

    • Escalate to the lead

  • WF-07 — Golden thread assembly. 1 human step, 4 automated steps, about 10 hours a month reclaimed.

    1. Step 1. Any project record created (SHAREPOINT)
    2. Step 2. Classify and index
    3. Step 3. Link to stage and decision
    4. Step 4. Check the record for gaps
    5. Step 5. Golden thread record (ARCHIVE)

    Risk points in this workflow:

    • Gap in the record. A missing link found at handover is expensive. Found the same week, it is nothing.

    Steps you still do:

    • Fill the gap

  • WF-08 — Party wall + notice tracking. 1 human step, 4 automated steps, about 3 hours a month reclaimed.

    1. Step 1. Adjoining owners identified (PROJECT)
    2. Step 2. Prepare the notices
    3. Step 3. Track service per owner
    4. Step 4. Log acknowledgements
    5. Step 5. Notice register (REGISTER)

    Risk points in this workflow:

    • Notice unacknowledged. An unacknowledged notice is not a served notice, and the programme assumes it is.

    Steps you still do:

    • Decide the next step

  • WF-09 — Site inspection reporting. 1 human step, 4 automated steps, about 6 hours a month reclaimed.

    1. Step 1. Site photos uploaded (MOBILE)
    2. Step 2. Sort by element and location
    3. Step 3. Draft the inspection report
    4. Step 4. Extract defects and instructions
    5. Step 5. Inspection report + snagging list (PROJECT)

    Risk points in this workflow:

    • Defect against an approved detail. A defect spotted on site and not written down is a defect nobody owns.

    Steps you still do:

    • Confirm the instruction

  • WF-10 — Meeting intelligence → decision register. 1 human step, 6 automated steps, about 5 hours a month reclaimed.

    1. Step 1. Site meeting recorded (TEAMS). 43 minutes, four attendees
    2. Step 2. Transcribe + attribute. Who said it, not just what
    3. Step 3. Extract decisions and actions. Separates a decision from a comment
    4. Step 4. Assign to a name and a date. Never to “the team”
    5. Step 5. Flag client changes as variations. Cost consequence surfaced now
    6. Step 6. Decision register entry. Dated, attributable, exportable
    7. Step 7. Minutes issued (OUTLOOK). Within the hour

    Risk points in this workflow:

    • Ambiguous decision. Flagged rather than recorded wrongly. A wrong entry in a decision register is worse than a gap.

    Steps you still do:

    • Confirm the ambiguous items

  • WF-11 — Fee proposal generation. 1 human step, 4 automated steps, about 4 hours a month reclaimed.

    1. Step 1. Brief structured (PROJECT)
    2. Step 2. Map scope to RIBA stages
    3. Step 3. Build the stage fee schedule
    4. Step 4. Draft, name and file the proposal
    5. Step 5. Proposal issued + tracked (OUTLOOK)

    Risk points in this workflow:

    • Proposal unanswered. A proposal with no follow-up is a lead you already paid to win, going cold.

    Steps you still do:

    • Approve and send

  • WF-12 — Enquiry capture + qualification. 1 human step, 4 automated steps, about 5 hours a month reclaimed.

    1. Step 1. Enquiry received (OUTLOOK)
    2. Step 2. Create the contact record
    3. Step 3. Identify typology and constraints
    4. Step 4. Qualify against your criteria
    5. Step 5. Response sent + call booked (CALENDAR)

    Risk points in this workflow:

    • Unqualified but urgent. The enquiry that does not fit the criteria is the one that gets forgotten, not the one that gets declined.

    Steps you still do:

    • Take it or decline it

  • WF-13 — Payment chasing. 1 human step, 4 automated steps, about 6 hours a month reclaimed.

    1. Step 1. Invoice passes due (XERO)
    2. Step 2. Check for part payment
    3. Step 3. Send a professional reminder (OUTLOOK)
    4. Step 4. Record every contact
    5. Step 5. Payment record + audit line (XERO)

    Risk points in this workflow:

    • Materially overdue. Money owed past a point is not a chasing problem any more, and someone senior needs to know.

    Steps you still do:

    • Decide the position

  • WF-14 — CPD logging. 1 human step, 4 automated steps, about 2 hours a month reclaimed.

    1. Step 1. CPD activity attended (CALENDAR)
    2. Step 2. Capture hours and subject
    3. Step 3. Attribute to the individual
    4. Step 4. Track against the practice record
    5. Step 5. Practice CPD record (REGISTER)

    Risk points in this workflow:

    • Individual behind on hours. Found in November it is a plan. Found in December it is a problem.

    Steps you still do:

    • Book what is missing

  • WF-15 — Practice dashboard. 1 human step, 4 automated steps, about 4 hours a month reclaimed.

    1. Step 1. Any workflow completes (AUTOARCH)
    2. Step 2. Aggregate by project and stage
    3. Step 3. Surface what is slipping
    4. Step 4. Compare against the fee schedule
    5. Step 5. Practice dashboard (AUTOARCH)

    Risk points in this workflow:

    • Project drifting. A project going quietly wrong is visible in the data weeks before it is visible in a meeting.

    Steps you still do:

    • Act on it

Hours reclaimed are our own estimates from building these, not measured client results — section 10 explains why we will not show you numbers we cannot stand behind.

12Investment

Fee proposal · AA-FEE-001 · REV 02INDICATIVE — VALID 30 DAYS FROM ISSUE

What this costs, before you talk to anyone.

Indicative bands, not a quotation — enough to know whether this is a conversation worth having, which is more than most agencies will tell you before a discovery call.

The alternative to automating this is usually a part-time practice administrator, or ten hours a month of a director’s time.

  • F1

    First workflow

    Start here

    One workflow, scoped and built.

    The process costing you most, mapped in writing before anything is built. Priced so it is not a board decision — we would rather you tested us on something small than committed to something large on trust you have no reason to give us yet.

    • Discovery and a written workflow map
    • One workflow built, tested and live
    • Four weeks from start to running

    Scope is locked at the map. If the map shows automation is the wrong answer, we say so and you owe nothing beyond it.

    Fixed fee. Agreed before work starts.

    £2,400

  • F2

    Each workflow after the first

    The second one, and the third.

    Discovery is already done and the integrations are already built, so each workflow after the first costs less than the first. This is the rung between one workflow and a whole stage — there is no jump to make.

    • Priced per workflow, agreed one at a time
    • Stop after any one of them
    • Runs on the connections already in place
    Per workflow. £1,500 each from the fifth.

    £1,800

  • F3

    Practice build-out

    A whole RIBA stage, or a whole function.

    Everything that touches money, or everything that touches compliance evidence, or everything a new project needs to start properly. Usually five to eight workflows, delivered in stages you approve as they come.

    • Five to eight workflows across one area
    • Integrated across your existing stack
    • Staged delivery, staged payment
    Staged. Each stage priced and approved before it starts.

    £9,000 – £15,000

  • F4

    Retained

    What the fee actually reserves.

    Named so you can see it is capacity rather than a subscription: at £600 we monitor what is running and fix it, replying by the next working day. At £1,200 we also hold half a day a month for changes and build one new workflow a quarter.

    • Monitoring, and fixes when something breaks
    • Next working day response, in writing
    • Reserved capacity for changes as your process changes

    No rollover. Cancel at a month’s notice and everything built stays yours.

    Per month. Three months minimum, one month notice.

    £600 – £1,200

Calculation — payback on the first workflow

Your figures, not ours
4 hrs
1 hrs40 hrs
£45/hr
£25/hr£150/hr
Hours a month, at the rate
4 × £45
Cost of doing it by hand, monthly
£180
Over a year
£2,160
First workflow, fixed fee
£2,400
£2,400 ÷ £180 a month

13.3 months

Assumes the workflow removes those hours completely. If it removes half of them, double the answer. The sliders start low on purpose.

Terms

Basis of charge
F1 and F2 are fixed fees agreed before work begins. F3 is staged, each stage priced and approved before it starts. F4 is a monthly retainer against reserved capacity.
Excludes
Third-party licence and subscription costs for systems you already run or choose to add. Any hardware. VAT, at the prevailing rate.
Payment terms
Half on appointment, half on the workflow going live. Staged work invoices at the end of each stage. Retainers invoice monthly in advance. Fourteen days.
Validity
Indicative figures, held for 30 days from the date of issue. A written quotation supersedes them.

We start with one workflow. If it works, we build the next. We are not asking you to replace anything on day one.

No email required

All figures exclude VAT · indicative only · fixed before work begins

Each line opens a scoping sheet — four clauses, two commercial and two technical, about fifteen questions. It ends in a written position rather than a call booking, and where your answers point at a different line than the one you clicked, it says so.

13Before / after

Without AutoArch

  1. Inquiry
  2. Outlook thread
  3. Someone remembers
  4. Excel
  5. Call
  6. Forgotten follow-up
  7. Manual proposal
  8. Drive folder
  9. Teams again
  10. “Where is that file?”

With AutoArch

  1. INQUIRY
  2. QUALIFIED
  3. CONSULTATION
  4. PROPOSAL
  5. ONBOARDING
  6. PROJECT
  7. DELIVERY
INQUIRYHANDOVER

One line. Nothing in between to remember.

ELEVATION · COMPLETED

Less managing.

Less chasing.

Less copying.

Less remembering.

More architecture.

AutoArch gives architecture and interior practices something software rarely gives them. Time back to design.

The blueprint

Your studio already has workflows.Let’s make them run themselves.

3 questions · your blueprint in under a minute

COMPLETED · AA-BLU-001:100