← Back to All Articles
2026-06-286 min read
ArchitectureGeneral LedgerEngineering

Why We Engineered a Monolith: The Anti-Silo Architecture of IHQ

How running 13 disparate SaaS tools across 40 staff nearly bankrupt our agency, and why single-database transaction locking is the only cure for operational chaos.

MK
Muhit Khan
Founder & Chief Systems Architect
## The Broken Agency Tech Stack In 2024, our digital agency in Dhaka was spending nearly $2,400 per month on fragmented software subscriptions: Asana for sprint tracking, HubSpot for CRM pipelines, Xero for accounting, Harvest for timesheets, and custom Zapier webhooks trying to glue them all together. Despite the cost, our data was never in sync. A project manager would mark a sprint milestone complete on Friday evening (`SK-07`), but our finance department wouldn't find out until Tuesday afternoon, delaying our milestone invoice (`SI-02`) by four days. Worse yet, our account managers had no real-time visibility into whether a client's retainer check had cleared before starting new sprint work. ## The Cost of Middleware When your core business logic relies on API webhooks and third-party middleware (`iPaaS`), you introduce three lethal vulnerabilities into your operations: 1. **Race Conditions:** If an employee updates their billable hourly rate while a timesheet sync is in flight, which database holds the truth? 2. **Reconciliation Lag:** General ledgers should never depend on asynchronous nightly batch jobs. Every billable hour must directly debit client WIP and credit internal labor costs instantaneously. 3. **Audit Blindspots:** Under strict NBR compliance in Bangladesh (`Musak 6.3`), any mismatch between your sequential invoice log and your VAT return triggers instant penalties. ## Enter the Single-Database Monolith We stopped trying to sync tools and decided to build one unified engine (`ADR-mkt-001`). By running all 13 core modules, from CRM lead intake to payroll disbursement, on a single, immutable PostgreSQL database schema, we achieved strict ACID compliance across every department. Now, the exact second a project manager drags a Kanban card to *Done*, the underlying employee timesheet (`BE-08`) is scored, the client's sequential VAT invoice is staged (`SI-02`), and the general ledger journal entry is posted (`GL-01`). Zero webhooks, zero latency, total peace of mind.
Published under IHQ Engineering Governance · All rights reserved.

See these engineering principles live in action.

Explore the 13 unified modules running on our single-database architecture.