Named customers, told in full
Where a customer has agreed to be named, the whole engagement: the challenge, what we built on Claude, the phases week by week, the proof it is in production, and what changed.
The stories
Each one is written from the engagement record: dates, phases, deliverables and the outcome the customer reported.
StockJarvis: A Claude intelligence layer inside India’s precision trading platform
StockJarvis’s research team went from raw tick-level backtests to polished strategy insight about 60 to 70% faster. Built on Claude and live inside their Strategy Lab, Simulator and Algo modules within one month.
Read the story →Branding, UX/UI and marketing studio, India and the Middle East10+Design Asylum Studio: The engineering partner behind a design studio, ten projects in
Design Asylum designs the brand and the experience. woodfrog builds what ships. Ten-plus projects together since 2025, from brand websites and e-commerce to internal tools and AI features inside client products, with Claude in the build where it earns its place.
Read the story →How a customer story differs from a case study
Both are real. They are written to different standards.
Anonymised, number checked
Published only where the customer’s own Finance team checked the figure. The customer is not named.
Named, told in full
The customer agreed to be named, and the story carries the whole engagement including the phases and the impact they reported.
Have a similar problem?
Tell our digital representative what is going on, or book the fixed-fee Week 1 audit. Either way you get a written view of what we would build first.