Case studies

The full story, including the parts that went sideways

Problem, research, architecture, database design, API flow, results and the lessons I actually took away - written for engineers and the people who fund them.

SaaS Platform

Softedin

Problem: Delivery knowledge lived in people's heads. Estimates drifted, margins were discovered after the fact, and no two projects were run the same way.

Read the case study

Estimate accuracy: +38%
Invoicing cycle: 6 days → 1
Reporting queries: sub-200ms

Realtime Platform

PEEQ

Problem: The original system wrote every ping straight to the primary database. At scale, dashboards timed out and history queries locked the write path.

Read the case study

Live map latency: < 800ms
Ingest throughput: 12k events/min
History query time: 31s → 0.4s

AI Product

Zizta

Problem: AI content tools produce confident, generic drafts. Teams could not tell which output was actually good before publishing it.

Read the case study

Editor agreement: 90%
Cost per brief: -61%
Draft-to-publish time: 4h → 25m

Growth Platform

ToolsZip

Problem: Free tools attract enormous traffic and destroy margins if every request touches an origin server.

Read the case study

Cache hit rate: 92%
Median response: 40ms
Infra cost / 1M runs: under $20

AI Product

HumanJot

Problem: Chat-window AI breaks the writing flow. Writers lose context, tone drifts, and edits are impossible to review.

Read the case study

Suggestion accept rate: 68%
Time to first token: 280ms
Weekly retention: +44%

Taking on 2 new partnerships for Q4

Want a write-up like this for your product?

Thirty minutes, no pitch deck. Bring the problem - you'll leave with an honest read on scope, risk and the fastest credible path to launch.

Book a discovery call WhatsApp