Skip to content
Fiescrow

Services

Eight things, done properly

Every one of these is backed by something we built and still run. Where a service has no product behind it, we say so.

Consulting

Advice on what to build, what to buy, and whether the thing you already have is worth keeping.

  • Architecture review
  • Due diligence
  • Roadmapping

Product Engineering

From a rough idea to a product in people's hands, then keeping it running.

  • Go
  • TypeScript
  • Python

AI Engineering

Assistants, agents and retrieval built into products, where they earn their place.

  • Python
  • Vercel AI SDK
  • OpenAI

Web Platforms

Multi-tenant SaaS, marketplaces and internal tools that hold up under real load.

  • Next.js
  • React
  • Vue

Mobile Apps

iOS and Android apps, from the first build to the store listing.

  • Flutter
  • Dart
  • Go

Games & Interactive

Game mechanics and progression systems, whether or not the thing is called a game.

  • Unity
  • C#
  • Flutter

Payments & Escrow

Multi-currency payments, wallets, payouts and escrow that holds money until work is approved.

  • Go
  • Laravel
  • Stripe

Digital Marketing

Search, content, campaigns, influencers and lifecycle email, measured against revenue.

  • GA4
  • Google Ads
  • Meta Ads

How it goes

The same five steps, whatever the service

Scoping is paid and self-contained. You keep what it produces either way.

  1. 01

    Scope

    A short paid engagement where we work out what the thing needs to do, what it can leave out, and roughly what it costs. You keep the output whether or not you continue with us.

  2. 02

    Shape

    Flows, screens and the data model, reviewed together before anyone opens an editor. This is the cheapest point at which to change your mind.

  3. 03

    Build

    Two-week cycles, each ending with something you can open and use. No status decks — the deployed version is the status.

  4. 04

    Ship

    Launch, store submission where it applies, and the monitoring you need to find out about problems before your users report them.

  5. 05

    Operate

    Fixes, iteration and support after launch. Or a clean handover with documentation, if you would rather take it in house.

Not sure which of these you need?

Describe the problem. Working out which of these it needs is our job.

Start a project