Production-tested project shapes — architecture, timeline, and team from week zero.
An archetype is a project pattern we've shipped enough times to know the shape: what gets built, how long it takes, who's on the team, and where the rollout typically breaks. Use these as a reference point when scoping a new engagement — most projects modify an archetype rather than start from a blank page.
Available archetypes
Each archetype below names a project type we've delivered. The detail page covers architecture choices, integration dependencies, common failure modes, and the phased rollout sequence that has worked in production. Use these as a starting brief — your actual scope will adjust per operation.
- 250-bed Hospital HMS RolloutPhased hospital management system rollout for mid-to-large private hospitals. OPD-first pilot, then layered IPD, lab, pharmacy, billing, and reporting modules. HL7/FHIR integration, multi-tier billing (self-pay, panel, insurer, corporate), JazzCash / Easypaisa / 1Link / UPI rails.
- Scope — OPD + IPD + lab + pharmacy + billing + reporting · NABH-aligned audit logs · on-prem or cloud
- Timeline — 8–10 weeks for OPD pilot · 4–9 months full multi-module rollout
- Team — Senior architect + 2 full-stack engineers + clinical SME embedded
- Multi-store POS RolloutPilot-store-to-fleet playbook for replacing legacy POS across 10+ stores without downtime. Offline-first sync, payment-rail integration (cards + wallets), inventory reconciliation, cash-up flow, and store-to-HQ rollout sequencing.
- Scope — POS terminals + inventory + payments + analytics · multi-store sync · returns + gift cards
- Timeline — 4 weeks pilot store · then 1–2 weeks per store rollout wave
- Team — Senior architect + 2 engineers + ops SME embedded for store rollouts
Why archetypes
Most enterprise software projects fail at scoping, not execution. The team commits to a date and a budget before they know what they're actually building — then the surprises show up in week 6. Archetypes are how we de-risk that: a recognized project shape with a known integration map, a phased rollout, and the team shape from week zero.
If your project matches an archetype, the discovery sprint is faster and the build is more predictable. If it doesn't, the archetype still helps — we know which assumptions don't carry over.