Case 01 — SaaS / Staff Augmentation

How we assembled a 3-dev team in 10 days for Viser Safety — and shipped 4 major features in 60 days.

Viser needed to take an existing safety audit SaaS to the next level fast. No team in place, bugs in the existing code, and a list of critical features blocking enterprise sales.

Week-by-week timeline

Day 1–3

Initial call + requirements scoping

We mapped the existing codebase (Laravel + Angular), identified critical bugs, and estimated scope for the first sprint. No surprises — we found 3 major bugs before the contract was signed.

Day 4–10

Team assembled and onboarded

1 PM + 2 full-stack developers started. We pushed for a 3rd developer by day 8 after estimating the dynamic forms module was larger than originally scoped. Client approved same day.

Week 3–6

Dynamic forms + role management shipped

The two highest-priority features went live in sprint 2. Dynamic forms required rebuilding the form renderer from scratch — the existing implementation wasn't extensible.

Week 7–10

Org chart + reporting module delivered

Both modules shipped on schedule. Reporting required integrating chart.js and building a custom export pipeline — added 4 days to the estimate, communicated proactively.

Ongoing

Retained as the core engineering team

Viser chose to continue the engagement. We're still the primary dev team as of 2026.

Key technical decisions

🔧

Rebuilt the form renderer instead of patching it

The existing dynamic form implementation was tightly coupled to a single use case. We recommended a full rebuild with a configuration-driven approach — added 5 days but made all subsequent modules 3x faster to build.

🧩

Chose Angular CDK for the org chart over a third-party lib

Every org chart library we evaluated had licensing issues or poor Angular compatibility. We built the tree visualization using Angular CDK drag-and-drop — more work upfront, fully owned by the client long-term.

Kept legacy API endpoints intact during the role management rewrite

The mobile app (not in scope) consumed several endpoints. Instead of breaking changes, we versioned the API and kept both versions live during the migration window.

What almost went wrong

⚠️

The original codebase had no test coverage

We discovered zero unit tests on day 2. The risk: changes to shared utilities could silently break existing features. We added a lightweight test layer in week 1 before touching anything critical — added 3 days, avoided at least 2 production incidents.

Result

Features shipped

4 major

Time to first deploy

17 days

On-time delivery

100%

Engagement

Ongoing

“They seem competent and deliver within a reasonable timeline of their estimates.”
— Ryder Wright, CEO · Viser LLC

Want us to do this for your product?

Book a free 20-minute call. We'll scope your project, recommend the right team composition, and give you a realistic timeline — no pitch, no pressure.

Book a Free Call →