Case study · Healthcare SaaS
A working product, built to prove one idea. The architecture had to support many.
A founder-led healthcare SaaS startup had spent several years building a working product and proving it with real test users. Growing beyond that first use case meant changing how the platform modelled care relationships — which called for senior technology leadership, not simply more code. D W Martin, LLC provided architecture, governance and hands-on engineering as one accountable relationship.
- Industry
- Healthcare SaaS
- Engagement
- Fractional Technology Leadership
- Focus
- Product architecture · Engineering governance · Cloud · Delivery
- Status
- Active engagement
The situation
A working product, at an inflection point
The platform worked. Several years of founder-led development had produced a healthcare application proven with real test users and deliberately focused on a single monitoring use case — one care relationship at a time. That focus was the right way to prove the idea. Growing past it asked more of the architecture than the startup phase had needed to build, and more of the engineering foundation than successive phases of fast delivery had left behind.
The architecture lived in people
Successive phases of delivery had outpaced the documentation. The knowledge was real and hard-won, but it lived with the people who built each part rather than in a shared record.
Decision history was not written down
Choices had been made well at each stage, but the reasoning behind them was not captured anywhere the next phase of engineering could pick it up.
Engineering work had no prioritized view
Improvements were understood individually, and had accumulated across successive phases, but there was no single inventory the owner could weigh against feature investment.
Development and production needed to converge
Moving fast was the right trade at an earlier stage. As the platform matured, the two needed a more controlled path back into alignment.
The engagement
Understanding came before building
Rather than starting with the requested software change, the engagement began by establishing what the platform actually did — and let what that revealed shape how the work would be governed. Everything after that was traceable.
Discovery
We began by establishing what was actually there — documenting how the inherited platform worked, and stating plainly what we had verified and what we had not. Evidence, not assumption, became the basis for everything after.
Governance
What discovery found shaped how the work would be run. We established how technical decisions would be made and recorded — so every later choice could be explained, reviewed and inherited.
Architecture
The monitoring model evolved from a single care relationship at a time to multiple simultaneous relationships across providers and organizations. Monitoring became traceable over time, so a patient could be monitored, released and monitored again without losing the history. Architectural decisions were recorded with their context and consequences.
Prioritization
Findings accumulated across successive phases of engineering were consolidated into a single prioritized register, giving the business owner a clear view of engineering priorities and modernization options.
Implementation
Feature work continued throughout. Delivery was never paused to accommodate the architectural work happening alongside it.
Assurance
Delivered work was independently verified before it was accepted, separately from the people who implemented it.
Controlled release
Production promotion became a governed, rehearsed, approved operation with a documented rollback position.
Continuing modernization
The engagement is active. Architecture, delivery and modernization work continues as the platform matures.
The final stage is deliberately open. This engagement is active and the work described here is continuing.
Why this was different
Technology leadership and hands-on engineering
Senior technology judgment and the engineering to act on it came from the same accountable relationship. Recommendations did not have to be handed to a separate organization to be interpreted.
Technology leadership
- Architecture authority
- Engineering standards
- Prioritization and sequencing
- Technical risk identification
- Release governance
- Executive technology guidance
One accountable relationshipD W Martin, LLC
Hands-on engineering
- Application engineering
- Cloud and infrastructure
- CI/CD and deployment workflows
- Automated testing
- Direct implementation
- Release assurance
What changed
Verified changes of state
Established
Engineering governance for the platform
Established
An authoritative architecture baseline for the platform
Evolved
A monitoring model that supports multiple simultaneous care relationships
First
Governed production release, executed and formally closed
How the work was done
Architecture-Led. AI-Accelerated. Human-Governed.
Architecture-Led
Understanding, architecture, risk and sequencing preceded implementation — and the architectural record was reconciled against what was actually built.
AI-Accelerated
AI-assisted engineering increased capacity for research, analysis, implementation, documentation and testing. It is how the work is delivered, not a claim about speed.
Human-Governed
Architecture authority, evidence review, approval and production accountability remained with people throughout. Nothing reached production without human decision.
Role and contribution
Who led the work
D W Martin, LLC provided the architecture and governance engagement, and David Martin, Founder and Principal, personally led the architecture and engineering-governance work. Implementation was carried out under that architecture and under review — the accountable technical judgement and the delivery did not sit with different parties.
Technology
What we worked with directly
These are the capabilities D W Martin, LLC exercised directly during the engagement.
- PHP / Laravel engineering
- Relational schema and migrations
- AWS and Kubernetes operations
- CDN delivery reliability
- CI/CD workflow engineering
- Automated testing
- Multi-factor authentication
- Role-based access control
Where the work stands
This engagement is active
The work below is deliberately separated. Nothing in the first column is in progress, and nothing in the second or third is presented as finished.
Completed and verified
- Engineering governance established
- Architecture baseline documented
- Engineering improvement register active
- First governed production release, formally closed
- New platform capability delivered and accepted
- Monitoring model evolved to support multiple simultaneous care relationships, traceable over time
Currently continuing
- Continued feature delivery
- Prioritized engineering improvement work
- Ongoing platform modernization and environment alignment
- Extending the platform beyond its first monitoring use case
Not part of current proof
- Further modernization work
- Remaining prioritized engineering improvements
Next step
Facing a similar decision?
If a working platform is reaching the point where it needs stronger architecture, governance and delivery discipline — without a full-time technology executive — that is a conversation worth having.