Has the file moved from the AE yet?
AI automation for Indian architecture + interior practices
Your software runs your projects.Nothing runs the gaps.
AutoArch builds the compliance and coordination layer between the tools your office already owns — sanction follow-up, stage-wise billing, drawing revision records, RA bill certification. Even the WhatsApp group.
Built by a team that has served architecture and interior practices for eight years. Working with firms across Delhi NCR.
02The architect's reality
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 firm we speak to owns a full stack. None of it covers the work that carries the risk — the deadlines, the records, 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 sanction file across eleven live projects and five authorities
- Proving which drawing revision the client actually signed off
- Linking a CoA stage sign-off to the invoice that should follow it
- Assembling the CC and OC file before somebody asks for it
- Chasing a consultant RFI that has gone quiet for nine days
- Certifying an RA bill inside the window the contract gives you
- Keeping a decision register from a site meeting that nobody minuted
- Logging CoA CPD hours before the renewal 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
- 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 CoA work stages, 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 ↓Scroll to advance the sequence →
Concept Design
Trigger
ENQUIRY · WHATSAPP · 09:14
Ground + 2 residence with basement — 325 sq m plot, Sector 57, Gurugram.
AutoArch fires
Sequence
- 01Captures the enquiry off WhatsApp
- 02Creates the contact record
- 03Identifies typology, plot size and authority
- 04Qualifies budget against scope
- 05Assigns to an associate
- 06Sends a personalised response
- 07Books the site visit
Enquiry to booked site visit · no one touched it
Preliminary Design & Estimate
Trigger
APPOINTMENT · CONFIRMED
Client appointed. Stage 2 opens.
AutoArch fires
Sequence
- 01Creates the client folder and structure
- 02Issues the appointment letter and fee agreement
- 03Raises the advance invoice with GST
- 04Checks the CoA registration on the signing set
- 05Requests consultant appointments
- 06Sets the stage-wise billing schedule
Project set up, and billed, before the first sketch
Drawings for Sanction
Trigger
OBPAS · FILE ACCEPTED
Building plan file accepted for scrutiny.
AutoArch fires
Sequence
- 01Arms the approval clock
- 02Opens the NOC and RFI registers
- 03Follows up with consultants who go quiet
- 04Logs every departmental objection as raised
- 05Escalates before the date, not after
The sanction file is now something watching you, not something you remember to ask about
Working Drawings & Tender
Trigger
DRIVE · 16:02
Kitchen_GFC_RevC.pdf lands in the folder.
AutoArch fires
Sequence
- 01Detects the revision
- 02Supersedes and archives Rev B
- 03Updates the GFC drawing register
- 04Assembles the tender and BOQ pack
- 05Tracks NOC validity against the programme
- 06Records who approved what, and when
The right drawing, provable eighteen months from now
Contractor & Construction
Trigger
SITE · RA BILL 04
Contractor submits. Certification window opens.
AutoArch fires
Sequence
- 01Checks quantities against measurement
- 02Reconciles against the BOQ rates
- 03Issues site instructions and logs them
- 04Turns the WhatsApp photo dump into a site report
- 05Assigns snags to a name and a date
Bills and site instructions on the clock, not in someone’s head
Completion & Handover
Trigger
WORK COMPLETE
Completion certificate application opens.
AutoArch fires
Sequence
- 01Assembles the CC and OC dossier
- 02Closes out the compliance record
- 03Issues the final bill and reconciles retention
- 04Files the decision register
- 05Archives the project, indexed
The record is finished because it was built as you went
Project brief
AUTO-GENERATED
- PROJECT
- Ground + 2 residence with basement
- PLOT
- Sector 57, Gurugram · DTCP plotted colony
- AREA
- 325 sq m plot · 780 sq m proposed built-up
- SCOPE
- CoA Stages 1–7
- BUDGET
- ₹2.4 – 2.9 crore construction cost
- TARGET
- Sanction 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, applies your own rate, names the file, sends it on email and WhatsApp, and keeps following up until there is an answer.
Fee proposal
AA-PRO-118 · REV 01
- CLIENT
- Mr. A. Ahluwalia
- PROJECT
- Ground + 2 residence with basement, Sector 57 Gurugram
- SCOPE
- CoA Stages 1–7
- FEE BASIS
- Lump sum per stage · 6% of project cost
- STAGE 1
- Concept Design
- ₹1,80,000
- STAGE 2
- Preliminary Design & Estimate
- ₹2,70,000
- STAGE 3
- Drawings for Sanction
- ₹3,15,000
- STAGE 4
- Working Drawings & Tender
- ₹4,20,000
- STAGE 5–6
- Contractor & Construction
- ₹2,85,000
- STAGE 7
- Completion & Handover
- ₹75,000
- SUBTOTAL
- ₹15,45,000
- GST
- Shown separately at 18%
- EXCLUSIONS
- Sanction and scrutiny fees · NOC charges · consultant fees · site survey · soil investigation
- TERMS
- Stage-wise, on completion of stage · CoA Conditions of Engagement · TDS as applicable
DRAWN
AUTOARCH
DATE
AUTO
SHEET
1 / 1
Saved as
Status
- SEND
- FOLLOW-UP
- REMINDER
- 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
The only human decision in this whole sequence.
- 01Project created
- 02Client folder
- 03Team assigned
- 04Project template
- 05Milestones
- 06Client welcome
- 07Kickoff meeting
- 08Payment schedule
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.
- Step 1. File lands in project folder (DRIVE). Listens on the issued-drawings folder
- Step 2. Parse drawing number + revision. Reads the title block, not the filename
- Step 3. Match against drawing register (REGISTER). Finds the superseded sheet
- Step 4. Supersede + archive Rev B. Moves, does not delete
- Step 5. Stamp issue sheet + audit line. Who, what, when, to whom
- Step 6. Notify the distribution list (WHATSAPP). Contractor, structural, PMC, client
- 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 — Sanction + statutory deadline tracking. 1 human step, 5 automated steps, about 9 hours a month reclaimed.
- Step 1. File accepted for scrutiny (OBPAS). Watches every live sanction file
- Step 2. Arm the approval clock. Statutory timeline recorded against the project
- Step 3. Poll for departmental objections. Daily, logged as raised
- Step 4. Track NOCs and clearances. Fire, AAI height, environment, lift — each its own item
- Step 5. Approval window closing. Escalates before the date, not after it. This is the point of the whole workflow.
- Step 6. Resubmit, revise or follow up. A judgement call, surfaced early
- Step 7. Sanction register updated. Every live file, one view
Risk points in this workflow:
- Approval window closing. Escalates before the date, not after it. This is the point of the whole workflow.
Steps you still do:
- Resubmit, revise or follow up
WF-10 — Meeting intelligence → decision register. 1 human step, 6 automated steps, about 5 hours a month reclaimed.
- Step 1. Site meeting recorded (MEET). 43 minutes, four attendees
- Step 2. Transcribe + attribute. English, Hindi or the mix people actually speak on site
- Step 3. Extract decisions and actions. Separates a decision from a comment
- Step 4. Assign to a name and a date. Never to “the team”
- Step 5. Flag client changes as extra items. Cost consequence surfaced now, not at final billing
- Step 6. Decision register entry. Dated, attributable, exportable
- Step 7. Minutes issued (EMAIL + WHATSAPP). 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.
- 01Site architect uploads photos
- 02AutoArch analyses and organises
- 03Site Report #018 generated
- 04Issues extracted
- 05Tasks assigned
- 06Client update generated
- 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
- 01DiscoveryWeek 1
We map your stages, your stack and where the time actually goes. Output is a written workflow map — yours either way.
- 02Workflow 01 builtWeeks 2–3
One workflow. The one costing you most, scoped to ₹75,000 fixed before anything starts.
- 03Live in your practiceWeek 4
Running against your real projects, with someone accountable when it matters.
- 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
AA-PRN-001 · REV 01

FIG 10.2 · PRINCIPAL
Ritik Poddar — Founder, AutoArch
Ritik has spent eight years building software for architecture and interior design practices across India, the UK and the US. Before AutoArch he built iDesign.Market, a project management platform for AEC and interior firms, and runs MarkTechRover, the studio behind it. AutoArch is what came out of watching the same problem repeat in practice after practice: the design work is world-class, and the drawing registers, specs, RFIs and handover documents are still held together by people re-typing things.
Founder vision
01 / 04
Most software sold to architects asks the practice to change shape to fit it. I think that’s backwards.
A 5-to-25 person practice already has a way of working that took years to earn. It doesn’t need another subscription with ninety features and three that matter. It needs a small number of things built precisely around how it actually runs — and it needs whoever builds them to still be there in three years.
So AutoArch has a rule: we never sell a practice something it has already solved. We start at the document and data layer, where the unbillable hours quietly live, and we earn the next step by making the first one work. One product at a time, built to sit inside the practice rather than beside it.
The ambition isn’t to be the software every studio uses. It’s to be the studio a few practices keep calling for the next decade.
Ritik Poddar · Founder
10.3 — Your data
AA-DAT-001 · REV 01
- D.01
- Residency
- Practice data is stored and processed in India. Nothing is moved outside the country without your written instruction — which matters if you work on government or PSU projects.
- 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 data processing agreement, drawn under the DPDP Act 2023, 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.
WF-01 — Sanction + statutory deadline tracking. 1 human step, 5 automated steps, about 9 hours a month reclaimed.
- Step 1. File accepted for scrutiny (OBPAS). Watches every live sanction file
- Step 2. Arm the approval clock. Statutory timeline recorded against the project
- Step 3. Poll for departmental objections. Daily, logged as raised
- Step 4. Track NOCs and clearances. Fire, AAI height, environment, lift — each its own item
- Step 5. Approval window closing. Escalates before the date, not after it. This is the point of the whole workflow.
- Step 6. Resubmit, revise or follow up. A judgement call, surfaced early
- Step 7. Sanction register updated. Every live file, one view
Risk points in this workflow:
- Approval window closing. Escalates before the date, not after it. This is the point of the whole workflow.
Steps you still do:
- Resubmit, revise or follow up
WF-02 — Stage-wise billing. 1 human step, 4 automated steps, about 7 hours a month reclaimed.
- Step 1. CoA stage signed off (PROJECT)
- Step 2. Match stage to the fee schedule
- Step 3. Draft the GST invoice (TALLY)
- Step 4. Attach the stage evidence
- Step 5. Invoice issued + logged (TALLY)
Risk points in this workflow:
- Stage payment not raised. A signed-off stage with no invoice behind it is unbilled work ageing quietly, and the client has moved on.
Steps you still do:
- Approve and release
WF-03 — RA bill certification. 1 human step, 4 automated steps, about 8 hours a month reclaimed.
- Step 1. RA bill submitted (CONTRACTOR)
- Step 2. Check quantities against measurement
- Step 3. Reconcile against the BOQ rates
- Step 4. Draft the certification note
- Step 5. Certification + payment advice issued (EMAIL)
Risk points in this workflow:
- Certification window closing. A bill certified late holds up the contractor, and a bill certified without measurement is a liability the architect signed.
Steps you still do:
- Certify
WF-04 — Revision control + evidence trail. 1 human step, 6 automated steps, about 6 hours a month reclaimed.
- Step 1. File lands in project folder (DRIVE). Listens on the issued-drawings folder
- Step 2. Parse drawing number + revision. Reads the title block, not the filename
- Step 3. Match against drawing register (REGISTER). Finds the superseded sheet
- Step 4. Supersede + archive Rev B. Moves, does not delete
- Step 5. Stamp issue sheet + audit line. Who, what, when, to whom
- Step 6. Notify the distribution list (WHATSAPP). Contractor, structural, PMC, client
- 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.
- Step 1. Approval requested (EMAIL + WHATSAPP)
- Step 2. Record what was sent, exactly
- Step 3. Remind on schedule
- Step 4. Capture the response verbatim, whichever channel it came back on
- 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.
- Step 1. RFI raised (REGISTER)
- Step 2. Log against the project
- Step 3. Set the response date
- Step 4. Follow up, politely, on a schedule (EMAIL)
- 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 — Compliance record assembly. 1 human step, 4 automated steps, about 10 hours a month reclaimed.
- Step 1. Any project record created (DRIVE)
- Step 2. Classify and index
- Step 3. Link to stage, NOC and decision
- Step 4. Check the record against the OC checklist
- Step 5. CC / OC dossier (ARCHIVE)
Risk points in this workflow:
- Gap in the record. A missing document found at completion certificate stage costs weeks. Found the same week, it is nothing.
Steps you still do:
- Fill the gap
WF-08 — NOC + clearance tracking. 1 human step, 4 automated steps, about 3 hours a month reclaimed.
- Step 1. Clearances identified for the project (PROJECT)
- Step 2. List every NOC the file needs
- Step 3. Track each application separately
- Step 4. Log issue dates and validity
- Step 5. NOC register (REGISTER)
Risk points in this workflow:
- NOC pending or lapsed. An expired fire NOC is not a held NOC, and the programme assumes it is. Sanction stops at the weakest one.
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.
- Step 1. Site photos uploaded (WHATSAPP)
- Step 2. Sort by floor, element and location
- Step 3. Draft the site visit report
- Step 4. Extract snags and site instructions
- Step 5. Site visit report + snag list (PROJECT)
Risk points in this workflow:
- Work not per approved detail. A deviation spotted on site and not written down is a deviation nobody owns, and it is the architect who gets asked.
Steps you still do:
- Confirm the site instruction
WF-10 — Meeting intelligence → decision register. 1 human step, 6 automated steps, about 5 hours a month reclaimed.
- Step 1. Site meeting recorded (MEET). 43 minutes, four attendees
- Step 2. Transcribe + attribute. English, Hindi or the mix people actually speak on site
- Step 3. Extract decisions and actions. Separates a decision from a comment
- Step 4. Assign to a name and a date. Never to “the team”
- Step 5. Flag client changes as extra items. Cost consequence surfaced now, not at final billing
- Step 6. Decision register entry. Dated, attributable, exportable
- Step 7. Minutes issued (EMAIL + WHATSAPP). 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.
- Step 1. Brief structured (PROJECT)
- Step 2. Map scope to CoA work stages
- Step 3. Build the stage fee schedule, GST shown separately
- Step 4. Draft, name and file the proposal
- Step 5. Proposal issued + tracked (EMAIL + WHATSAPP)
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.
- Step 1. Enquiry received (WHATSAPP)
- Step 2. Create the contact record
- Step 3. Identify typology, plot size and authority
- Step 4. Qualify against your criteria
- 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 follow-up. 1 human step, 4 automated steps, about 6 hours a month reclaimed.
- Step 1. Invoice passes due (TALLY)
- Step 2. Check for part payment and TDS deducted
- Step 3. Send a professional reminder (EMAIL + WHATSAPP)
- Step 4. Record every contact
- Step 5. Payment record + audit line (TALLY)
Risk points in this workflow:
- Materially overdue. Money owed past a point is not a follow-up problem any more, and a partner needs to know.
Steps you still do:
- Decide the position
WF-14 — CoA registration + CPD logging. 1 human step, 4 automated steps, about 2 hours a month reclaimed.
- Step 1. CPD activity attended (CALENDAR)
- Step 2. Capture hours and subject
- Step 3. Attribute to the individual
- Step 4. Track CoA registration renewal dates too
- Step 5. Office CPD + registration record (REGISTER)
Risk points in this workflow:
- Registration or hours behind. A lapsed CoA registration is not an administrative problem — an unregistered architect cannot sign the drawing the sanction file needs.
Steps you still do:
- Book what is missing
WF-15 — Practice dashboard. 1 human step, 4 automated steps, about 4 hours a month reclaimed.
- Step 1. Any workflow completes (AUTOARCH)
- Step 2. Aggregate by project and stage
- Step 3. Surface what is slipping
- Step 4. Compare billed against the fee schedule
- 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 Monday 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
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 full-time project coordinator, or ten hours a month of a principal’s time.
- F1Fixed fee. Agreed before work starts.
First workflow
Start hereOne workflow, scoped and built.
The process costing you most, mapped in writing before anything is built. Priced so it is not a partners’ 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.
₹75,000
- F2Per workflow. ₹45,000 each from the fifth.
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 function — 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
₹55,000
- F3Staged. Each stage priced and approved before it starts.
Practice build-out
A whole CoA stage, or a whole function.
Everything that touches money, or everything that touches sanction and 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
₹2,75,000 – ₹4,50,000
- F4Per month. Three months minimum, one month notice.
Retained
What the fee actually reserves.
Named so you can see it is capacity rather than a subscription: at ₹20,000 we monitor what is running and fix it, replying by the next working day. At ₹40,000 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 lock-in. Stop at a month’s notice and everything built stays yours.
₹20,000 – ₹40,000
Calculation — payback on the first workflow
Your figures, not ours- Hours a month, at the rate
- 12 × ₹500
- Cost of doing it by hand, monthly
- ₹6,000
- Over a year
- ₹72,000
- First workflow, fixed fee
- ₹75,000
12.5 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 — Tally, Zoho, Microsoft 365, WhatsApp Business API messaging charges. Any hardware. GST, 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. TDS deducted at source is fine — share the certificate.
- 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 GST · 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
- Inquiry
- Outlook thread
- Someone remembers
- Excel
- Call
- Forgotten follow-up
- Manual proposal
- Drive folder
- Teams again
- “Where is that file?”
With AutoArch
- INQUIRY
- QUALIFIED
- CONSULTATION
- PROPOSAL
- ONBOARDING
- PROJECT
- DELIVERY
One line. Nothing in between to remember.
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