Book a scoping call →
Solutions by outcomeNever miss work26Every call, lead and enquiry answered, routed or captured.Get paid faster32Money collected, matched and reconciled without chasing.Fill the diary12Fewer no-shows, fuller weeks, less phone tag.Answer without staff16The repeated questions handled, the rest escalated.Join up the systems77Data entered once, moving everywhere it is needed.Verify and secure15Real customers in, fraud and fakes out.Prove you are compliant8Obligations met by default, evidence captured automatically.Run it for me12Someone watching, someone answering, every month.
Solutions by capabilitySMS & messaging28Voice & call flows22Verification & identity13WhatsApp & chat5Video & telehealth4Email & notifications4Flow automation3Unified conversations2Contact centre5Delivery & tooling2Compliance & records5Workflow automation49Trade & job management8Applied AI8Self-hosted platforms7Payments & billing29Run it for me4
All 198 builds Describe it in plain English Venture models Instant scope & price Free tools Search everything Connections Integration guides Workflow library By integration Partnerships Contract roles Honest comparisons Field notes Work we have built Colabs How it works Platforms & licensing Pricing Book a scoping call
Home / Work / ABYSS — Surf Forecasting Backend
Data products Colabs ventureBuilt, deployment gated

ABYSS — Surf Forecasting Backend

A physics-grounded surf forecast backend, built test-first through nine phases.

What we set out to build

A forecast that models the physics rather than reprinting someone else's feed.

What was built

  • Nine phases built test-first, each gated on the previous one
  • A physics model verified against worked examples rather than assumed correct
  • Database-dependent phases identified and held rather than faked

What it achieves

  • A worked example in the source material turned out to be wrong, and the implementation matches the correct value with the discrepancy documented
  • The gated phases are marked as gated rather than shipped untested
The hard part: Finding that the reference material's own worked example was off, and having to decide whether to match the book or match the physics.

The stack

TypeScript, Supabase, vitest.

Common questions

How was this built?

This was built through Colabs, our sister company. A founder brought the idea and the domain knowledge, Colabs brought the team, the founder funded the build with a monthly subscription, and they hold equity in the company that resulted. We label every case study, because a studio that publishes its prices and argues the other side of its own comparisons has to be equally precise about its own portfolio.

What state is it in?

Built, deployment gated. We state that plainly rather than describing everything as production: several things here are deliberately gated, and the reason is usually evidence rather than a missing feature.

Can you build something like this for us?

That is the point of publishing it. The same patterns are in the catalogue at published prices, and you can scope your own version on the plain-English page without contacting us first.

Where to next

If something here is close to what you need, the same patterns are in the catalogue at published prices, or you can describe your version in plain English and get it scoped and priced without talking to anyone.

Want something like this built?

The catalogue prices the patterns behind this work. Describe your version and the engine will scope it, including an allowance for anything nobody has costed.

Describe it in plain English → See all work