Skip to content

Cases

What we can show publicly — the rest in discovery.

Three NDA-safe mini-cases: problem, approach, and qualitative outcome. Named customers, logo walls, and sharp percentages wait on clearance. Deeper proof we show live in a conversation.

Mini-cases

Three patterns we can stand behind in public.

Anonymised and without invented numbers. If you recognise the problem, this is typically where we have depth — and in discovery we show work that looks like yours.

  • Illustration of multi-tenant data isolation — separate organisations under one platform.

    B2B SaaS

    Multi-tenant before sales outruns the architecture

    The problem
    A SaaS product grew past its first customers. Suddenly organisations, roles, and data isolation were required — while the original model still thought one user at a time.
    Approach
    We introduced organisation scope in queries, RLS in Postgres, tightened auth, and prepared SSO without breaking existing tenants.
    Outcome
    New customers could onboard into their own organisation with clear isolation — and the team got a pattern they could extend instead of ad hoc fixes.
  • Illustration of a modern marketing site focused on speed and SEO structure.

    Web & SEO

    Marketing site out of a heavy CMS

    The problem
    The site lived in WordPress with a heavy theme/plugin stack. Updates were slow, Core Web Vitals were red, and marketing wanted speed without losing ranking.
    Approach
    We migrated to Next.js with URL mapping and 301 redirects, SEO parity from day one, and a headless CMS marketing could write in.
    Outcome
    Editors could publish without a deploy queue, pages became faster to deliver, and organic visibility was preserved through cutover.
  • Illustration of edge and cloud infrastructure focused on visibility and control.

    Cloud & ops

    A cloud bill with no owner

    The problem
    The monthly cloud bill had risen without a clear explanation. Tagging was sparse, there were no budget alerts, and nobody dared turn resources off for fear something important would break.
    Approach
    We mapped the top cost drivers, set tags and alerts, removed zombie resources, and proposed a simpler host split by workload — not by hype.
    Outcome
    The team could see what drove cost, and the next changes were reviewed before they hit the bill — without cutting what carried the business.

What we deliberately skip

No logo wall. No invented percentages.

The three mini-cases above are anonymised patterns we can defend in a conversation. Named customers and screenshots from their products ship only when they sign off.

The deepest proof is still discovery: live systems, architecture diagrams, code samples, and — on request — a reference call. That is a better buying process than a marketing page that promises results it cannot document.

What we show in a conversation

Concrete — without the marketing gloss.

30–60 minutes, NDA if needed, and you get a much clearer picture of whether we are the right match than any logo wall would give you.

  • Live demo of systems we have built

    We show working products, customer portals, or infrastructure — not only screenshots. With client permission or on our own systems.

  • Anonymised architecture diagrams

    If NDA prevents showing the client concretely, we can show technical architecture without named data — it shows how we think, not who we built for.

  • Code samples and pull requests

    Concrete examples of how we solve the problem you have — multi-tenant patterns, billing flows, RAG retrievers, whatever it is.

  • Reference call with an existing customer

    On request we can put you in touch with a customer at a similar stage or in a similar industry. We ask first; you get an honest impression.

  • An honest assessment of fit

    If your problem is outside our expertise, or you would be better served by another team, we say so in the conversation — not after a quarter.

References

On request we can put you in touch.

We have customers who will take a short call with potential new customers about what it is like to work with us. We ask first, and we pick the one closest to your stage or industry.

Say the word when we talk — it is typically a good idea after the discovery conversation, once we know whether we are the right match.

Let's talk concretely

The best case is the one we walk you through live.

Write a few lines about what you are facing. We honestly assess whether it is for us, and if it is, we show concrete work that looks like yours.