National clinical registry modernised
A national clinical registry rebuilt behind a strangler pattern, with the data migration reviewed and signed off line by line, and 14 clinics onboarded in the first wave.
Capability · Epcotec
Application development
Full-stack web apps, portals, APIs, dashboards: React/Next.js, Node, Python, Go. Delivered by named senior engineers, fixed scope, staging from week one.
What we deliver
Scope, in plain terms.
Full-stack portals and dashboards
Role-based portals and operational dashboards built end to end, from data model to interface, on React and Next.js frontends with Node, Python or Go services behind them.
Typed REST and GraphQL APIs
Versioned, documented APIs with generated types shared end to end, contract tests in CI, and load budgets agreed with callers so integrations do not surprise anyone at launch.
Design systems and accessible frontends
Component libraries in React and Next.js with keyboard paths, contrast and screen reader behaviour tested, so accessibility holds as the product grows instead of degrading one screen at a time.
Realtime dashboards and live views
Live operational views over WebSockets and server-sent events, with backpressure, reconnection and stale-data states designed, so the board stays honest when the feed slows or drops.
Progressive modernisation of legacy UIs
Strangler-pattern migration that replaces screens module by module behind one domain, keeping the old system running until each piece is proven, with rollback planned before cutover, not after failure.
Plain-language interfaces
Interface copy written for first-time users and auditors alike, free of internal jargon, with error messages that say what happened and what to do next, in plain words.
Rough time estimate
Window: 4-12 weeks
Team: 2 full-stack engineers
Complexity: M
Indicative only. A fixed price follows a free 30-minute scope review.
Get a fixed quoteDelivery process
Fixed scope. Weekly demos. Staging from week one.
Week 0-1 · Discovery & fixed-scope SOW
Scoping sessions on users, workflows and integrations, then a fixed-scope statement of work with milestones, load budgets and the acceptance criteria your team will sign against.
Week 1-3 · Architecture & design system
Data model, service boundaries and the component library agreed early, so screens are assembled from tested parts instead of redrawn from scratch each sprint.
Week 1-5 · Weekly demos, staging from week one
Staging runs from week one and demos land every week, so direction is corrected on working software in days rather than rediscovered at acceptance.
Week 4-10 · Hardening, accessibility & load tests
Security review, accessibility audits with keyboard and screen reader passes, and load tests against agreed budgets, with every finding fixed and re-verified before we call it done.
Week 10-12 · Handover & 30 days support
Runbooks, monitoring and architecture notes handed over with a walkthrough session, then 30 days of support while your engineers take the pager.
Benchmark deliveries
Proven in this discipline.
Exactly-once market data pipelines
Go pipelines moving market data with idempotent offsets giving exactly-once processing semantics, verified by reconciliation, so no feed produced duplicates or gaps under broker restarts.
ERP overlay integration layers
Overlay integration layers built on the strangler pattern, adding modern portals and workflows over ERP systems without forking master data, decommissioned modules tracked and retired on schedule.
More evidence in the delivery history and the complete 734-engagement register.
FAQ
Asked before signing.
How do you keep scope and price fixed?
Discovery ends in a signed statement of work with milestones and acceptance criteria. Changes are handled as explicit variations, so the agreed price stays the agreed price.
What does staging from week one mean in practice?
A running environment exists by the end of week one, and every weekly demo happens on it. You review working software on real data paths, not mock-ups or slide decks.
How do you handle accessibility compliance?
Keyboard paths, contrast and screen reader behaviour are tested as part of the build, with audits in the hardening phase and every finding fixed before handover, evidenced in writing.
Who owns the code and can we maintain it?
You own everything, including infrastructure definitions and tests. Handover includes runbooks, architecture notes and a walkthrough, followed by 30 days of support while your team takes control.
Talk to the engineers.
No account managers. Your message lands with the people who would deliver it, and you get a straight answer within one business day.
Book a discovery call →