From a mandate to a product your teams can build.

A board has approved a direction: a stablecoin, a tokenized product, a new payment flow. Nobody has yet written down what the product is, what the applicable regulation requires, and what to build first. Product strategy is that work: the decision, the architecture and the roadmap, written so your business, risk and engineering teams can act on them.

For

Banks, payment institutions, fintechs and digital asset platforms preparing a new product or entering a new market.

You get

A product brief your board can approve, a regulatory constraint map, a target architecture and a sequenced roadmap.

How we work together

A milestone-based mandate for the design phase, or senior expertise embedded in your product team.

Define, de-risk, deliver. Three pillars, one product.

Every product strategy mandate answers three questions, in this order. Each card shows what we cover and what you leave with.

01 / Pillar Build, partner or buy

Define the product.

Decide what the product is, who it serves, what it will not do, and whether to build, partner or buy, before budget is committed. We write the trade-offs down so the decision can be defended.

Scope
  • Product brief
  • Users and journeys
  • Build, partner or buy
  • Market and licence sequencing
  • Exclusions
  • Business case inputs
  • Decision memo
You leave with
  • Product brief
  • Build, partner or buy decision memo
  • User journey maps
  • Scope and exclusions agreed by business, risk and technology
02 / Pillar MiCA · DORA · GDPR

Design what the rules require.

Translate the applicable regulatory requirements into product constraints: what the licence allows, what must be recorded, who may hold what, where data may sit, and which checks run at each step. tracee is not a law firm; the map is confirmed with your counsel.

Scope
  • Regulatory constraint map
  • Licence perimeter
  • KYC and AML/CFT placement
  • Travel Rule
  • GDPR and data residency
  • DORA and critical providers
  • Questions for counsel
You leave with
  • Regulatory constraint map, each rule as a requirement with an owner
  • Compliance scope placed in the flow
  • Licence and perimeter note
  • Open questions for your counsel
03 / Pillar Architecture · roadmap

Plan a delivery your teams can execute.

Turn the decision into a target architecture and a roadmap with phases, owners, dependencies and the decision that gates each release, so engineering builds what risk has approved.

Scope
  • Target architecture
  • Systems and data flows
  • Third parties and vendors
  • Phasing and dependencies
  • Decision gates
  • Owners per workstream
  • Oversight through delivery
You leave with
  • Target architecture with the reasoning behind each choice
  • Delivery roadmap with phases, owners and gates
  • Platform and vendor shortlist
  • Milestone oversight, if you keep us on

How the mandate runs, and what you hold after each phase.

Four phases, each closed by a written decision before the next one starts. Open a deliverable to see what is inside.

Interviews with business, technology, risk and compliance, and a read of everything that already exists: mandate, licences, systems, previous attempts.

Decision gateScope and questions agreed.

A framing note: the options on the table, the constraints, and the questions the decision phase must answer.

What the product is and is not, and whether to build, partner or buy, taken to your decision-makers. Nothing is designed until the brief is approved.

Decision gateProduct brief approved by your decision-makers.
Product briefWhat is inside
  • Scope, users and value, in a few pages
  • What the product will not do, and why
  • Build, partner or buy, with the trade-offs scored
  • One recommendation, with its reasons
Regulatory constraint mapWhat is inside
  • Each applicable rule, written as a product requirement with an owner
  • The licence perimeter and what sits outside it
  • KYC, AML/CFT, Travel Rule and GDPR checks, placed in the flow
  • Open questions for your counsel

Target architecture, user journeys and compliance scope, in working sessions with your product, risk, compliance and engineering teams.

Decision gateDesign signed off by business, risk and technology.
Target architectureWhat is inside
  • Systems, data flows and third parties, with the reasoning
  • Where each control runs and who owns it
  • Integration points with your existing systems
  • Options rejected, and why
User journey mapsWhat is inside
  • Client, operator and back-office flows, end to end
  • Onboarding to exit, step by step
  • The gaps marked, each with an owner
  • The checks each journey triggers
Platform and vendor shortlistWhat is inside
  • Build, partner or buy, scored on cost, control and time
  • Providers compared against your requirements
  • The recommendation, with its reasons
  • Exit terms to negotiate

The roadmap and a decision memo, presented to the people who approve. Then your teams build; we can stay on to oversee the milestones.

Decision gateRoadmap approved; delivery ready to start.
Delivery roadmapWhat is inside
  • Phases, owners and dependencies
  • The decision that gates each release
  • What your committee approves at each gate
  • Where tracee oversees and where your teams deliver

Why tracee.

Builder's view

We have built what we design.

tracee began as a stablecoin payment infrastructure on Stellar that won the Circle Impact Award. We write product strategy knowing what breaks once a product is live.

Depth

12 patents across six jurisdictions.

The engagement lead, Bassel Assaad, PhD, is an engineer and inventor with a doctoral background in IT and systems. Read the founder bio.

Current mandate

Capital and product architect.

For a digital asset platform with a South African regulatory footprint, from product design to capital structure.

Frequently asked

Common questions about product strategy.

What is product strategy for a digital asset product?

The work that decides what to build before anyone builds it: the product's scope and users, what the applicable regulation requires, the architecture it needs and the order of delivery. It ends in documents your business, risk and engineering teams can act on, not in slides.

Can we start with the decision only?

Yes. The framing and decision phases end with a product brief and a regulatory constraint map your committee can approve. You can stop there, continue into design under a new scope, or take the brief to your own teams.

Do you replace our product team?

No. We work alongside it. We bring regulatory and architectural depth; your team keeps ownership of the product and the decisions.

Do you give legal advice on the licence?

No. tracee is a consulting firm, not a law firm. We translate the applicable regulation into product requirements and list the questions for your counsel, who confirms the legal reading.

How long does it take, and how is it priced?

After the discovery call, a scoping document follows within a week and fixes the deliverables, milestones and timeline. The design phase runs as a fixed-scope, milestone-based mandate; an embedded engagement on a daily rate suits teams that want senior expertise inside the room.

Can you stay through delivery?

Yes. Under a milestone-based mandate we oversee each milestone, including review of code, contracts and counterparties, and keep the architecture current as the programme evolves. Your teams or your integrator build and run the production systems.

Start with a conversation.

Thirty minutes, no slide deck, no obligation. Tell us what you are trying to build, and we will tell you whether we can help.