Services

Everything we do, written down

Five practices, thirty-six services — what each is for, and what you receive. If it is not here, we say so rather than learn it on your budget.

What this page is not

A catalogue lists capability; it does not prove it. No metrics or client stories here, deliberately.

See selected work

Practice 01

AI Engineering

AI systems that survive contact with production — not demos.

We build on foundation models and adapt them where evidence supports it. We do not train foundation models.

Practice 02

AI Advisory & Enablement

Making AI land in strategy, tooling, teams and risk.

Governance covers technical and organisational readiness; legal opinions come from your counsel. The people who score your readiness can implement the roadmap — or hand it to your engineers.

Practice 03

SaaS & Product Engineering

The product itself — from first release to multi-tenant scale.

Practice 04

Mobile Engineering

Built for the device fleet you actually support.

Cross-platform is a genuine choice, not one answer: Flutter for pixel-precise interfaces, React Native for JavaScript-strong teams, Kotlin Multiplatform for shared logic under native UI. We write the recommendation down, with its cost. Kotlin and Compose are our Android default.

Practice 05

Platform, Cloud & Data

The foundations that make everything above reliable.

How the work is shaped

Engagement models

Every engagement opens with a written engagement brief: outcome, scope, timeline, practice lead.

Flourisher engagement models, when each fits, and how it works
Model When it fits How it works
Fixed-scope project Scope well defined Agreed scope, timeline and outcome, quoted after discovery.
Flexible delivery Scope will evolve Work done at agreed rates; scope adapts each sprint.
Dedicated product team Multi-quarter product work A cross-functional squad reserved for you, monthly.
Embedded specialists You have a team, missing a skill Named specialists join your team, under your management.
Ongoing partnership Maintenance, SRE, AI operations Fixed monthly capacity, agreed response time, shared backlog.
Discovery sprint or workshop Assessments, strategy, enablement Time-boxed, with the deliverable pack agreed up front.
Audit and roadmap Before committing to a build Short and fixed-scope, ending in a plan you own.
Outcome-based Rare — objective measures only Tied to an agreed metric. Proposed sparingly — few outcomes are cleanly attributable.

No rate card here, and there will not be one — quoting before scope is guessing. Engagements start with a short paid discovery.

After the build

Three options once it ships

Pick one, and change your mind later if it stops fitting.

Maintenance

Keep it running. Dependency and SDK upgrades, security patching, crash triage, an agreed response time.

Growth

Keep it moving. Standing capacity against a jointly owned backlog, the same practice lead, the same shipped log.

Handover

Take it in-house. Documentation, the decision record, a recorded walkthrough, pairing with your engineers. No lock-in.

Handover is a real option, not a threat. Several arrangements we like best began as one.

Not sure which of these you need?

Most people arrive with a symptom, not a spec. Thirty minutes usually finds the right practice — and whether we are the right people.

Book a 30-min scoping call