Custom SaaS

An Australian architecture firm (5-10 architects, ARC-registered, NSW-based, servicing residential + commercial clients, projects $100k-$500k contract value) bills in ARC-aligned project stages. Stage model is standard: Schematic ($30-50k), Design Dev ($45-75k), Construction Docs ($50-100k), Contract Admin ($20-30k), Completion ($15-25k) = ~$160-280k per project average. Multiple concurrent projects (8-12 projects per year, overlap = 8-12 projects in flight simultaneously, staggered stage completion). Current practice: partner maintains spreadsheet tracking % completion per stage (architect updates: "Stage 2 is 75% done, ready for client review"), partner calculates invoice ($45k × 75% = $33.75k due), partner manually creates invoice in MYOB, adds to client list, emails invoice, client pays (or doesn't, 2-3 week payment lag is normal). Drawing revisions are chaos (architect works in Archicad, exports plan PDF, emails to client + structural engineer + MEP consultant, client sends feedback ("move the bedroom window 1m east"), architect edits Archicad, exports new PDF, re-emails (but forgets to CC structural engineer), structural engineer is still using old revision, engineer's coordination notes don't match architect's new design, clash is discovered mid-construction, rework costs $15k). Sign-offs are informal (architect calls client: "drawings are ready," client emails back "looks good," but no formal approval trail, later client disputes: "I never approved the bathroom tile spec, that's not what I wanted," argument ensues, architect can't prove approval). Sub-consultant work is offline (architect emails Revit file to structural engineer, engineer downloads, works locally on their own computer for 2 weeks, email back revised file, architect manually compares old vs new file to find changes, merge is manual, next revision cycle takes another 2 weeks). Retainers are forgotten (client has $5k/month retainer for "ad-hoc architectural advice," first month is billed, second month invoicing is late, client pays anyway, but third month partner forgets to invoice, month 4-5 go unpaid until partner chases, relationship is strained). Licensing compliance is ignored (architect's ARC registration expires, partner doesn't notice, architect is legally practicing without current registration, someone audits the firm, $5k fine, partner frantically renews). NCC compliance is manual (partner reads NSW Building Code, adds custom checklist to project file, manually checks items off as they're addressed). Current setup: 8 projects in flight, average 4 months per project lifecycle = 8 projects × 4 months = 32 project-months of billable time annually. Revenue: 32 project-months × $150/month billing rate (based on $45k ÷ 3 months average) = $4.8M revenue capacity (if perfectly utilized). Actual billable rate (due to coordination overhead, revision rework, billing delays, compliance admin): ~70-75% utilization = $3.36M-3.6M actual revenue. Costs: 5 architects @ $120k salary = $600k/yr. 1 project manager @ $80k = $80k. 1 admin @ $60k = $60k. 1 technical designer @ $70k = $70k. Office overhead (rent, utilities, software licenses Archicad $5k/yr per seat × 5 = $25k, Microsoft 365 $5k, insurance $30k, phone/internet $10k, accounting $15k) = $85k. Total costs: $600k + $80k + $60k + $70k + $85k = $895k/yr. Gross margin: $3.36M - $895k = $2.465M/yr gross profit. Hidden bleed: (1) Revision coordination overhead—architect spends 2-3 hours per revision cycle managing versions, re-sending emails, chasing structural engineer for feedback, resolving clashes. 8 projects × 8 revision cycles per project × 2.5 hours = 160 hours/yr wasted on version management = at $100/hr billable rate (architect cost) = $16k in unbilled overhead. (2) Billing delays—invoices are created 2-3 weeks after stage milestone. Client pays 1-2 weeks after invoice. Total delay: 3-5 weeks per stage × 4 stages per project = 12-20 weeks delay per project × 8 projects = 96-160 weeks total delayed cash = $3.36M revenue divided by 52 weeks = $64.6k/week average revenue, delay of 96-160 weeks is nonsense (but practically, average 3-5 week delay per invoice = 5 invoices per project = average 3-5 week delay on $150k per project = $8.6k-$14.4k in delayed receivables per project × 8 projects = $68.8k-$115.2k in total delayed cash flow at any given time). (3) Admin overhead—partner spends 8-10 hours/week on invoicing, compliance, retainer chasing, license tracking, NCC checkbox = 400-500 hours/yr = at $150/hr (partner rate) = $60k-$75k in unbilled admin. (4) Sub-consultant coordination inefficiency—each revision cycle takes 2 weeks (architect emails, engineer works offline, emails back, architect merges manually). If coordination was real-time (comments sync live), cycle could be 3-4 days. Savings per cycle: 10-11 days. 8 projects × 8 cycles = 64 cycles × 10 days saved = 640 days = 128 weeks = $3.36M ÷ 52 weeks × 128 weeks = $8.28M in "unlocked revenue" IF every day of saved coordination could be billed (unrealistic, but shows magnitude). Conservative: 25% of that = $2.07M additional capacity (or, same team completes projects 25% faster, cycles out next project, higher utilization). Total annual bleed: $16k revision management + $68.8k-$115.2k delayed receivables + $60k-$75k admin overhead + $2.07M in unlocked revenue (if you wanted to scale) = $144.8k-$206.2k in annual inefficiency. Custom platform: unified stage-fee contract (client contract is JSON: {stages: [{name: "Schematic", fee: 40000, milestone: "50% complete"}, {name: "Design Dev", fee: 60000, milestone: "100% complete"}, ...]}. When architect marks "Schematic 50% complete" in system, system auto-triggers invoice generation, sends to client automatically, documents "approved on [date]"). Automated billing calendar (system tracks all 8 projects' stage milestones, color-codes due dates, auto-generates invoices on-date, no partner intervention required). Drawing revision control (architect exports from Archicad to AWS S3, previous version is auto-archived, version history shows "Rev A (Jan 15), Rev B (Jan 20), Rev C (Jan 28, current)," old revisions are labeled "archived," all team members always see current revision). Client portal (client logs in, sees all current drawings, sees revision history, can download any revision for reference, submits revision request via portal form, architect is notified, architect addresses request, marks request "complete," client approves with digital signature, approval is logged with timestamp). Sub-consultant real-time coordination (structural engineer downloads Archicad file once, logs into custom system, sees assigned drawings, uploads commented file or uses web-based markup tool, architect sees comments in real-time, comments are threaded by drawing section, engineer can see architect's replies immediately, next revision from architect is uploaded, engineer downloads new version, cycle time is 3-4 days instead of 2 weeks). Retainer tracking (recurring monthly charge on Stripe auto-charges client, system allocates 10-20 billable hours per month, client portal shows "10 hours consumed this month, 10 remaining, next month budget resets to 20," surplus hours roll to next month with a 3-month expiry, client can download usage report, no surprises, partner does 0 invoicing work). ARC compliance dashboard (system auto-tracks ARC license expiry dates per architect, 6-month alert before expiry, project checklist auto-generates NCC items per project type, architect checks off items as work is done, audit trail is digital, compliance report is exportable for external audit). Build cost $120-180k. Year 1: $120-180k. Year 2: $3k AWS hosting + $4k Stripe processing (on ~$3.6M billing, 0.11% processing fee) = $7k. Break-even: month 18-24. Year 2+ savings: $16k revision management + $68.8k-$115.2k delayed-receivables eliminated + $60k-$75k admin overhead saved = $144.8k-$206.2k/yr net positive. Plus 25% unlocked capacity (if 8 projects now complete in same time as previous 6, that's 33% more projects, more revenue, same staff). Conservative: $180k-230k/yr net positive by year 2.

Why Archicad + Procore Fall Short for Mid-Size Architecture Firms

Archicad (design software, $2k-$4k per seat per year, focuses on 3D modeling + drawing generation) and Procore (construction management SaaS, $300-$500/month, focuses on contractor field management + RFI tracking) are both industry tools, but neither is designed for the architect's billing lifecycle + stage-gated project delivery. Archicad does drawings beautifully, but doesn't track version history across email forwards (architect exports PDF, emails to 5 people, 5 versions exist, system doesn't know which is current). Procore is designed for contractors (field teams, safety, punch lists), not architects (design phases, milestone billing, consultant coordination). Missing pieces for architects: (1) Stage-fee milestone billing—Procore has contract tracking, but doesn't auto-invoice when "Stage 2 is 75% complete." You still manually create invoices. (2) Drawing revision control—Archicad has file versioning internally, but exports PDFs to email, version trail is lost. No central "all revisions are here, old ones are archived" dashboard. (3) Client portal for sign-offs—neither has formal client approval workflow. Client approval is "client emails back yes" or verbal phone call. (4) Sub-consultant real-time coordination—Procore is contractor-focused (subcontractors on-site doing work), not consultant-focused (structural engineer, MEP engineer, working offline on their own files). (5) Retainer billing automation—neither tracks recurring monthly billing with hourly allocation. (6) ARC compliance tracking—neither has built-in ARC registration expiry alerts or NCC compliance checklists. Archicad + Procore combo might seem complete (one for design, one for construction), but they don't bridge the architect's specific workflow: design phase → approval phase → documentation phase → handoff phase. Gaps in the pipeline mean manual overhead at every transition.

What Custom Replaces: Six Features Architecture Firms Need

1. Stage-Fee Milestone Billing & Automatic Invoice Generation

Client signs contract (JSON-based, editable in system): "Project: Medical Centre Renovation, Total Fee: $160k. Stage 1 Schematic: $40k (trigger: 50% complete), Stage 2 Design Dev: $50k (trigger: 100% complete), Stage 3 Docs: $50k (trigger: 100% complete), Stage 4 Admin: $15k (trigger: handover), Stage 5 Completion: $5k (trigger: warranty docs submitted)." Project starts Jan 1. Architect works on schematic design, creates floor plan, site analysis, materials palette. By Feb 15, architect assesses: "schematic is 50% done, ready for client review." Partner logs into system, marks "Stage 1: 50% complete." System auto-triggers: (1) Invoice generation: "Medical Centre Renovation - Stage 1 Schematic (50% complete), $40k due." Invoice is sent to client's email + appears in system ledger. (2) Client notification: system sends client SMS + email: "Your stage 1 invoice is ready for review. Amount: $40k. View invoice: [link]." Client clicks link, sees invoice, pays via bank transfer or credit card (system has Stripe integration). (3) Cash flow is immediate (client is already expecting stage payment, stage completion is objective milestone, payment comes within 3-7 days instead of 2-3 week delay with manual invoicing). By Mar 31, architect completes design development (100% done), adds structural coordination notes, refines specifications. Partner marks "Stage 2: 100% complete." System auto-generates $50k invoice. Client receives invoice day-of, pays by mid-April. By May 30, construction documents are finalized. Partner marks "Stage 3: 100% complete." System auto-generates $50k invoice. By mid-July, architect provides final on-site comments, RFI responses resolved. Partner marks "Stage 4: 100% complete." System auto-generates $15k invoice. By mid-August, punch list is complete, warranty docs are signed, handover is final. Partner marks "Stage 5: 100% complete." System auto-generates $5k invoice. Total: $160k invoiced by staggered milestones (Jan+Feb, Mar+Apr, May+Jun, Jul+Aug, Aug+Sep). Cash is collected on-time, no delays, no chasing. Manual system: Partner waits until Stage 1 is fully approved by client (May 10, not Feb 15), then manually creates invoice ($40k), emails to client, client pays May 25. Stage 2 invoice created Jun 10, client pays Jun 28. Revenue is lumpy, late, uncertain. Custom system: Stage 1 invoice Feb 15, paid by Feb 22. Stage 2 invoice Mar 31, paid by Apr 7. Revenue is predictable, smooth, on-time. Advantage: smooth cash flow, faster payables (can pay architect salaries on-time without waiting for end-of-project cash injection). Plus, staged billing aligns with client expectations (architecture projects have natural stage breaks, clients expect to pay per stage, not lump sum at end). Plus, contract is auditable (if client later claims "I didn't approve stage 2," system shows timestamp of approval, invoice date, payment date, full audit trail).

2. Drawing Revision Control & Version History Archive

Architect works in Archicad all day (creates floor plans, elevations, sections, details). By end of day, architect has new design (widened kitchen, added bathroom, relocated bedroom). Architect clicks "export to cloud" in custom system (integrated into Archicad as plugin, or just a "drag-drop" interface). System auto-uploads current Archicad file to AWS S3, generates PDF + DWG exports, creates new "revision" entry: "Design Development - Rev B, Jan 20, 2026 09:15 AM, Uploaded by [architect name]." Previous version (Rev A) is auto-archived (file is still accessible, but marked as "historical, not current"). Client portal shows: "Current: Design Development Rev B (Jan 20). Previous: Rev A (Jan 15)." All team members (structural engineer, MEP consultant, client contact) are notified via email: "New revision: Design Dev Rev B is ready. Download PDF: [link]." Structural engineer logs into system, downloads Rev B PDF, spends 2 days reviewing. Engineer emails feedback: "Recommend shifting the main column 0.5m east to avoid future rework." Architect reads feedback, opens Archicad, adjusts column, re-exports to cloud (now Rev C, Jan 22). Engineer is notified: "Rev C is ready, column is shifted." Engineer downloads Rev C, approves ("looks good"). By end of week, revisions are 5-6 cycles deep (Rev A, B, C, D, E, F). Client asks: "can I see the original concept from week 1?" System retrieves Rev A (historical), client downloads. Client: "I prefer the kitchen from Rev C, but the bedroom from Rev E." Architect understands instantly (rev history is visible, can compare, no confusion). Manual system: Architect exports plan, emails to 5 people. Next revision, architect exports new plan, can't remember to delete old version, emails new version to 5 people, but forgets to CC structural engineer on one email. Structural engineer is still using Rev A, gives feedback on old design, architect spends 1 hour explaining "that's rev A, we're on rev C now," wasted time. Or engineer spends 2 days reviewing old design, work is wasted. Or client sees 3 different PDFs in email chain, confused which is current, asks "which version should I approve?" Nobody knows. Or version control is manual: someone creates "Plan_v1, Plan_v2_FINAL, Plan_v2_FINAL_FINAL, Plan_v3_actually_final," nobody can tell which is the actual current version. Custom system: all revisions are timestamped, archived, accessible, current version is always clearly marked, zero confusion. Saves 2-3 hours per revision cycle in email management + clarification = 16-24 revision cycles per year × 2.5 hours = 40-60 hours/yr saved at $100/hr = $4k-$6k annual value.

3. Client Portal & Digital Sign-Off Tracking

Client (owner/developer) logs into custom system (credentials sent at project start). Portal shows: "Medical Centre Renovation Project. Status: Design Development (Rev B approved on Jan 20). Next: Construction Documents (ETA Jan 28). Current drawings: [floor plan, elevations, sections, MEP coordination, structural plans]. All drawings are here, organized by discipline." Client downloads floor plan, reviews with interior designer, finds: "the entry vestibule is too small, increase by 1.5m." Client logs back into portal, clicks "Revision Request," fills form: "Entry vestibule is 4m wide. Interior designer recommends 5.5m to accommodate staff flow. Can we increase?" Architect is notified (email + dashboard alert). Architect reviews request, assesses feasibility (yes, shifts structure slightly), updates Archicad, exports new plan (Rev C). System notifies client: "Revision request 'vestibule width' is addressed in Rev C. Download new plan: [link]. Approved? [Approve] [Reject] [Comment]." Client downloads, shows to interior designer, confirms: "looks good." Client clicks [Approve], system records: "Revision approved by [client name], Jan 22, 09:30 AM." Architect sees approval, proceeds. No email trail, no back-and-forth confusion, approval is logged. By week of Feb 15, all revisions for schematic design are resolved. Architect initiates final sign-off: system sends client formal approval form: "Schematic Design (Rev B) is complete. Approve to proceed to Design Development? [I Approve] [I Request Changes]." Client clicks [I Approve]. System captures: client name, timestamp, digital consent (not a signature, but legal acknowledgment in Australia via email is often sufficient, or system can integrate e-signature via DocuSign if higher formality is needed). Approval is logged: "Schematic Design approved by [client] on Feb 15." Architect sees approval, sends follow-up email: "thanks for approval, design development starts now, ETA 6 weeks." Signed artifact is archived (if dispute later: "client never approved," system shows approval record with timestamp, client can't claim ignorance). Manual system: Architect finishes schematic, calls client: "designs are ready, can we schedule a meeting?" Client takes 1 week to find time. Meeting happens Feb 22 (late). Architect presents drawings on laptop. Client says: "vestibule is too small, can you make it bigger?" Architect says: "sure, I'll adjust." Meeting ends, architect has notes on paper + recording (maybe). Architect goes home, redesigns, sends email with 3 PDF files (old and new version, unclear which is which). Client sees 3 PDFs, confused, forwards to interior designer, interior designer responds "vestibule looks good now." Architect assumes approval, proceeds to design development. 2 months later, client claims: "I never approved the bathroom layout, there's no bathtub window." Architect says: "I have your email saying 'looks good.'" Client disputes: "that email was about the vestibule, not the bathroom." Argument. Blame. Relationship damage. Custom system: approval is formal (approval form, timestamp, no ambiguity). Revision requests are documented (client requested "bigger vestibule," system shows it was addressed in Rev C, client approved Rev C). Approval is auditable. Zero disputes.

4. Sub-Consultant Real-Time Coordination & Drawing Markup

Architect completes schematic floor plan (Jan 20, Rev A). Architect assigns this drawing to structural engineer (in custom system, architect clicks "assign to: Structural Engineering Consultant"). System notifies engineer: "You've been assigned: Schematic Floor Plan Rev A. Download: [link]. Any comments? Upload markup or use web interface." Engineer downloads Archicad file or PDF, spends 2 days reviewing. Engineer considers: "main beam location is OK, but I'd recommend a column here instead of there to avoid spanning issues." Engineer opens web markup tool in system, selects floor plan area, adds comment: "Propose column at grid D-3 instead of D-4 (reduces 8m span to 5m). Avoids future rework. FYI: structural fee remains same." Architect is notified instantly (email + dashboard alert). Architect opens system, sees engineer's comment (with annotation on the floor plan). Architect replies: "Column at D-3 works, shifts space plan slightly. I'll adjust floor plan and upload Rev B tomorrow." Engineer sees reply immediately (no delay). Architect adjusts Archicad, uploads Rev B (Jan 23). Engineer downloads Rev B, sees column moved to D-3, approves: "looks good, we can proceed." Cycle time: 2 days review + 1 day revision + 0.5 day approval = 3.5 days. Engineer has only downloaded file twice (minimal overhead). Manual system: Architect emails Archicad file to engineer (Jan 20). Engineer opens file on their computer, works offline for 2 days, manually reviews, makes notes in Word document, emails architect: "I recommend column at D-3 instead of D-4." Architect reads email, opens their Archicad file (still at old column location), adjusts to D-3, exports new file, emails to engineer. Engineer downloads, but doesn't open (too busy). 5 days pass. Architect follows up: "did you get the new column layout?" Engineer replies: "no, I'll check tomorrow." Engineer finally opens file (Jan 28), confirms: "yes, D-3 works." By then architect has already created other drawings based on old column location. Rework required. Cycle time: 8 days (vs 3.5 days with real-time). Wasted 4.5 days per cycle. 8 projects × 4 cycles per project = 32 cycles × 4.5 days = 144 days = $3.6M ÷ 365 days × 144 days = $1.42M in delayed capacity (or, 25-30% longer project duration per project). Custom system: comments are threaded, real-time, non-blocking (engineer can continue other work while waiting for architect's response). Comments are tied to specific drawing areas (no "column comment is in email, but which column?"). Download/upload cycles are minimized (engineer downloads once or twice per stage, not once per revision). Saves ~4.5 days per cycle × 32 cycles = 144 days = 28 weeks of project duration eliminated = 28 weeks × $3.6M ÷ 52 weeks = $1.92M in unlocked capacity annually (or, 25-30% faster delivery on all projects, happier clients).

5. Retainer Billing with Hourly Allocation & Auto-Renewal

Client (developer, recurring relationship) signs retainer contract: "$5k/month, 20 billable hours/month, ongoing architectural advice + ad-hoc design tweaks." Month 1 (January): system auto-charges client's Stripe card on Jan 1 ($5k). System allocates 20 hours to client's budget. Architect logs time via system: "Jan 5: attended client meeting about site planning, 2 hours." Time is logged against client, deducted from 20-hour budget. "Jan 12: created 3 conceptual site plans for future phase, 4 hours." Budget is now 20 - 2 - 4 = 14 hours remaining. "Jan 20: reviewed client's MEP consultant's proposal, 1.5 hours." Budget is now 12.5 hours remaining. By Jan 31, architect has logged 18 hours (2 hours remaining). Month 2 (February): system auto-charges client again ($5k). Budget resets to 20 hours. But Jan had 2 hours unused, so system shows "20 hours available + 2 carryover hours = 22 hours available in February." System has a 3-month carryover cap (so client doesn't accumulate unlimited unused hours over years). Client can view portal anytime: "You have used 18 hours in January (90% of 20 allocated). 2 hours carryover available in Feb. Monthly rate: $250/hour ($5k ÷ 20 hours)." No surprises. If architect exceeds 20 hours in a month (say 22 hours), system flags: "You have exceeded Feb allocation by 2 hours. Overage: 2 hours × $250 = $500. This will be invoiced in March." Client's invoice in March shows: Feb retainer ($5k) + Feb overage ($500) = $5.5k. Client understands. No surprises. Renewal: month 12, contract is set to auto-renew. System alerts: "Medical Centre retainer renews Feb 1. Amount: $5k/month. To cancel or modify, reply by Jan 25." Client has 1-week notice. Client usually auto-renews (continuity of retainer is valuable). Month 13 continues seamlessly. Manual system: Partner manually creates retainer invoices in MYOB. Partner forgets to create Feb invoice. Client doesn't chase (assumes it'll come). Mar 1 comes, client hasn't paid Feb, partner is now embarrassed to send invoice (client might ask "why is this late?"). Partner sends "apology" invoice for Feb. Client pays. But by month 4, partner again forgets (busy with project work), client notices unpaid invoice in their AP system, client's accountant flags: "why is this unpaid?" Client asks architect "what's going on?" Relationship friction. Or partner tracks hours manually (architect writes "2 hours client call" in notebook), partner later guesses: "probably 20 hours total," may be wrong. Hourly allocation is murky, no transparency. Custom system: retainer is monthly auto-charge (no forgetting), hourly allocation is transparent to client (portal shows usage), overage is auto-calculated, renewals are auto-triggered with notice, zero admin overhead from partner.

6. ARC Compliance & NCC Tracking (NSW-Specific)

Australia: architects must be registered with ARC (Architects Registration Board of NSW). Registration is annual, expires on a fixed date. Firm has 5 architects: Architect A (expires Dec 2026), Architect B (expires Jul 2025), Architect C (expires Dec 2024), Architect D (expires Mar 2025), Architect E (expires Sep 2026). System auto-tracks all expiry dates. System alerts partner: (1) Architect C expires in 30 days (Nov 24). Partner must arrange renewal by Dec 24. (2) Architect D expires in 60 days (Jan 25). (3) On each expiry date, system double-checks: "Architect C's registration expired today. Is it renewed? [Yes, renewed] [No, expired, ALERT]." If not renewed, system sends URGENT alert: "Architect C is practicing without current registration. This is illegal. Renew immediately." If partner confirms [renewed], system updates record. Plus, if architect practices without current registration (even 1 day), firm can be fined $5k-$20k (per project). Manual system: Partner keeps a spreadsheet (or sticky notes). Partner forgets. Architect C's registration expires Dec 24, partner doesn't notice. January project starts, Architect C is billing hours, working on project. Regulator audit (random) happens Feb 1, auditor checks architect licenses, finds: "Architect C's registration expired Dec 24, still working Jan-Feb." Fine issued: $10k + investigation. Architect C is legally not allowed to practice, project work is invalid (may need re-certification or rework). Nightmare. Custom system: auto-track, auto-alert, auto-documentation. Zero fine risk. NCC (National Construction Code): Australian building code. Projects must comply with NCC2022 (or latest version). Architect must verify design meets NCC (structural, fire safety, accessibility, energy efficiency, etc.). System auto-generates NCC compliance checklist per project type (residential house = 25 items, commercial building = 50 items). Architect checks off items as work is done: "NCC compliance: (1) Floor levels comply with accessibility standards, check. (2) Fire separation walls are minimum 60 min, check. (3) Emergency exits are minimum 1000mm width, check..." By end of design phase, architect has checked all items, NCC compliance is verified. System generates "NCC Compliance Report, Jan 2026 - Jan 2027: 8 projects completed, all 8 projects have NCC compliance verified. Zero non-compliant projects." Report is audit-ready (if external auditor or regulator asks "are you NCC-compliant?" architect hands over report, proof is instant). Manual system: architect prints NCC standard document (200+ pages), reads through, manually checks off items on paper, paper is filed in project folder. Year later, firm is audited. Auditor asks: "show me NCC compliance for project X." Partner searches folder, paper checklist is found (but half the items are blank, illegible handwriting, unclear if "check" means compliant or not). Auditor: "you don't have clear documentation of compliance." Fine or warning issued. Custom system: digital, timestamped, clear, audit-proof.

Architecture Firm Economics & ROI Calculation

Typical mid-size firm (5 architects, 3 support staff, 8-12 projects per year, $3.6M annual revenue): Current costs: 5 architects @ $120k = $600k. 1 project manager @ $80k = $80k. 1 admin @ $60k = $60k. 1 technical designer @ $70k = $70k. Office overhead (rent $24k, utilities $8k, Archicad licenses $25k, Microsoft 365 $5k, insurance $30k, phone/internet $10k, accounting $15k, miscellaneous $8k) = $125k. Total costs: $600k + $80k + $60k + $70k + $125k = $935k. Revenue: 8-12 projects × $200k average fee = $1.6M-$2.4M gross. But with hidden bleed: $16k revision management overhead + $68.8k-$115.2k delayed receivables + $60k-$75k admin overhead + implicit 25% capacity drag (if coordination was instant, could complete 10 projects in same time as current 8) = net revenue loss of ~$160k-$250k annually. Effective revenue: $1.6M-$2.4M - $160k-$250k = $1.35M-$2.25M (lower than stated). Gross margin: $1.35M-$2.25M - $935k = $415k-$1.315M net profit (varies widely based on project success + billing timeliness). Custom platform cost: $150k upfront (average of $120k-$180k range). Year 1: $150k. Year 2: $7k hosting + processing = $7k. Break-even: 12-18 months (if firm saves $100k-$150k in year 1 from faster billing + reduced admin). Year 2 onwards: custom system saves: (1) $16k revision management (no more email version confusion). (2) $68.8k-$115.2k delayed receivables eliminated (invoices are on-time, payments are immediate, no 3-5 week lag). (3) $60k-$75k admin overhead (partner is no longer spending 10 hours/week on invoicing + compliance + retainer tracking, can focus on business development or project oversight). Total annual savings: $144.8k-$206.2k. Plus, 25% capacity improvement (if 8 projects can be done in same time as previous 6.4 projects, that's 1.6 extra projects per year = 1.6 × $200k = $320k additional revenue if utilization stays at 70%). Conservative estimate: $180k-$250k net positive annually by year 2. Build once ($150k), year 2+ is 100-167% ROI annually.

Six FAQs

Can we use custom platform alongside Archicad, or do we need to replace Archicad?

Keep Archicad. Custom system integrates WITH Archicad (plugin exports files to cloud, or manual upload interface). Architect's workflow is unchanged (design in Archicad, export at end of day). System handles revision control, sharing, approvals, billing. Archicad is the design tool, custom system is the project management + billing layer. No replacement needed, pure addition.

What if sub-consultants don't want to log into a new system?

Give them options: (1) Web-based markup (no login, share link for markup tool, engineer markup comments, system auto-syncs to Archicad project). (2) Email integration (engineer gets email with PDF, marks up in Adobe/Markup tool, emails back, system auto-collects comments). (3) Traditional file upload (engineer does work offline, uploads revised file, system detects changes). Not all consultants need to log in (system can work around their preferences). Goal is architect's workflow efficiency, not forcing everyone into new software.

How do we handle projects that don't fit the 5-stage model (e.g., small renovation, only 2 stages)?

Custom contracts are flexible. Instead of 5 stages, define 2 stages if that's the project scope. Contract JSON: {stages: [{name: "Design", fee: $30k}, {name: "Documentation", fee: $20k}]}. System auto-generates 2 invoices at those milestones instead of 5. Same logic applies to unusual projects (fast-track projects, design-build, etc.). Contract is fully customizable per project.

What if client doesn't want to approve digital sign-offs in the portal?

System can export approval form as PDF, client prints + signs by hand, sends back. System records: "approved by [client], [date], signature attached." Or client approves via email (system screenshots email approval, archives as evidence). Digital portal is preferred (faster, cleaner), but system accommodates traditional approval if needed.

Does the system handle variations and change orders?

Yes. Partner can create change order document (additional fee, revised scope), send to client via portal, client approves (or rejects). Approved change order is logged. Invoice is auto-adjusted (original fee + approved variation). Scope creep is visible (client can see "original fee $200k + variation $20k = new fee $220k"). No ambiguity about who agreed to what and when.

Can we use this for design-build projects where we're coordinating contractors, not just consultants?

Partially. System is designed for consultant coordination (structural engineer, MEP, etc.) where feedback is comments + revised drawings. Contractor field management (safety, inspections, punch lists, RFIs from site) is different workflow (Procore is better for that). Custom system covers pre-construction phases (design + documentation). For full design-build + construction management, integrate custom system (design + approvals) with Procore (field + construction) via API (both systems share project data, no manual sync).

The Bottom Line

Archicad is a great design tool, but it doesn't manage the architect's stage-gated billing, client approvals, consultant coordination, or compliance tracking. Procore is a great field management tool, but it's built for contractors, not architects. Mid-size architecture firms (5-10 architects) suffer from endemic chaos: stage milestones are late, invoices are delayed 3-5 weeks (cash flow is lumpy), drawing revisions are unversioned (clashes happen mid-construction), client approvals are informal (disputes arise), sub-consultant coordination is offline (projects slip 25-30% longer than necessary), retainers are forgotten (admin overhead is high), and ARC/NCC compliance is manual (audit fines happen). Custom platform costs $120-180k upfront, $7k/yr hosting + processing. Break-even month 18-24. Year 2 onwards: saves $144.8k-$206.2k annually in efficiency (faster billing, less admin, better coordination). Plus 25% capacity improvement (complete projects faster, cycle out new projects, higher utilization, higher growth). At $3.6M annual revenue, custom saves $180k-$250k/yr net positive by year 2. Build once ($150k), year 2+ is 100-167% ROI. Ready to automate your architecture firm? Check Aidxn's custom software packages, or book a call to discuss your firm's specific workflow (how many concurrent projects?, current stage-fee chaos?, sub-consultant coordination pain points?, retainer clients?, ARC compliance gaps?), and growth targets (scale to 10 architects?, expand to second office?, deliver projects 30% faster?).