Skip to content

Product strategy, design and engineering

Operating globally

We build the productsbusinesses need next.

  • Payments
  • Crypto & Web3
  • Markets
  • Sport
  • Property
  • AI

II · The proof

So what have you actually built?

II · The count

Numbers wecan be held to

These figures come straight from the products themselves, and every one of them appears again in that product's own block below. Nothing is projected, combined across products or rounded up.

  • $0.0MsettledPepay
  • 0.0KtransactionsPepay
  • 0.0Kwallets that have paidPepay
  • 0villas presented in one siteLinton Villas
  • 0tokens accepted, no payer feesBNBPay
  • 0products builtQuantar
  • 0in production todayQuantar
  • 0platforms indexedNoise
II · The proof

Products we'veput into production

Payments, crypto, trading infrastructure, combat sports, property investment and enterprise AI. All six are shown running.

01Multi-chain payments

The payment infrastructure turning crypto into something people can actually use.

Accept any supported asset and settle from one system — invoicing, payment links, QR checkout, subscriptions and reconciliation on the same ledger.

  • Cross-chain
  • Settlement
  • Treasury
  • Payment links
  • Subscriptions
  • AI payments

$19.9M settled · 75.9K transactions · 26.7K wallets that have paid

React · TypeScript · Solana · BNB Chain

The Pepay ecosystem

Accelerated by

  • Binance Chain
  • YZi Labs
  • CoinMarketCap
02Trading infrastructure

The infrastructure that makes real-world assets easier to buy, sell and trade.

Tokenisation solved issuance. It did not solve liquidity: it makes an asset digital without making it easy to trade. DRK is the layer between tokenised assets and the institutions that trade them.

  • Fair value
  • Liquidity
  • Risk
  • Execution
  • Settlement
  • Reporting

Wallets · Pools · Execution · Reconciliation · Reporting

TypeScript · React · EVM · Trading infrastructure

Networks and assets integrated

  • Ethereum
  • Solana
  • Aptos
  • Sui
  • USDC
  • Robinhood
  • Cantor
03Programmable payments

The payment network built for a world where money moves on-chain.

The BNBPay app on a phone, showing invoice generation, subscription creation and the x402 Flex multi-token acceptance form.
The BNBPay gift card screen on a phone, showing a USDC card preview and the four steps of sending a card by shareable link.

Payments that move on-chain without the payer covering blockchain fees — invoices, subscriptions, gift cards and API payments for merchants, platforms and AI agents across BNB Chain and opBNB.

  • Multi-token
  • x402 Flex
  • Gasless
  • Gift cards
  • Subscriptions
  • Merchant APIs

Six tokens accepted, with no blockchain fee for the payer

Solidity · TypeScript · Next.js · BNB Chain

Accelerated by

  • Binance Chain
  • YZi Labs
04Sports media platform

A platform for following combat sports, the fighters and the events.

Events, fight cards, rankings, athlete profiles and predictions across every major promotion, from announcement through to result.

  • Events
  • Fight cards
  • Rankings
  • Predictions
  • Athlete profiles
  • Community

Events · Full cards · Rankings · Predictions · Community

Next.js · TypeScript · Postgres · Prisma

Official partners

  • BATL Promotions
  • Box IQ
  • Kong Fight Tape
05Property marketing

A thirty-eight villa resort in South Lombok, presented online for overseas buyers.

We built the experience the developer sells through: masterplan, villa types, floor plans, financial projections, an eight-minute film and the full prospectus, as one guided journey.

  • Investor website
  • Guided sales journey
  • Masterplan & villa types
  • Financial projections
  • Interactive property tour
  • Investor prospectus

38 villas, four types and the full prospectus in one site

Strategy · UX/UI · Next.js · Interactive media

06Enterprise AI

One place for your team's email, chats, meetings and documents.

Everything the team works in is brought together and indexed, so context is found in seconds instead of hunted across a dozen disconnected systems.

  • Email
  • Chat
  • Meetings
  • Documents
  • Knowledge graph
  • Context engine

Email, chat, calls, documents and calendars in one index

React · Fastify · Postgres · Vector search

Connected platforms

  • Gmail
  • Outlook
  • Slack
  • Teams
  • Drive
  • Dropbox

III · The approach

And what makes those hold up once they are live?

III · The approach

We build digital products for lasting performance — not just launch day.

Products don't stay still. Customers change, requirements change and new problems appear. We build for the version that exists in three years, not the one that launches.

How we work

From uncertainty todependable software

Four capabilities, one accountable team. Strategy, design and engineering stay connected from the first decision through production.

  • Work out what the business is trying to achieve, who it is for, what limits it and how success gets measured.

    The most expensive product decisions are often made before anyone realises they are making them.
  • Shape the interface, the way information is organised and the system underneath it together — not as separate jobs passed between teams.

    A design is not finished when it looks right. It is finished when it still works when the data is messy, the edge cases arrive and the network does not.
  • Ship in working pieces, each one tested and monitored from the day it goes live.

    Build the codebase for the engineer who inherits it eighteen months from now. Often, that engineer is you.
  • Keep improving the product against what real use shows and what the business needs next.

    Production teaches you things the original specification never could. The advantage belongs to teams that keep listening.

IV · The studio

So who is actually doing the work?

IV · The studio

The people you meetare the peoplewho build

The same team stays with the work from the first idea through to the finished product, so you are always talking to the people making the decisions.

  • No junior team replacing the people you met

  • No account managers sitting in between

  • No handoff from sales to a different team

  • No technology chosen because it is fashionable

How an engagement starts

Fourteen days. Four fixed outputs. Enough clarity to decide what happens next — and nothing you cannot walk away from.

  1. Day 01 — 02

    The problem, restated

    A precise definition of what the business is trying to achieve, written in language everyone involved can agree on.

  2. Day 03 — 05

    The constraint map

    We map what we know, what we are assuming and what still needs an answer — with every assumption written down.

  3. Day 06 — 09

    A working first version

    One important part of the product, built end to end and deployed. Real enough to expose the technical, product and operational problems before you commit to building everything.

  4. Day 10 — 14

    The decision

    A written recommendation showing the trade-offs, risks and next steps — with a plan another capable team could execute without us.

You leave with a decision. Not another deck.

What you leave with

Every output is yours, whether we continue together or not. No lock-in. No dependency. No obligation.

IV · The breadth

Noise

Private beta

DRK

In development

Pepay

$19.9M settled

Linton Villas

38 villas presented

Combat Reviews

Every major promotion

BNBPay

Six tokens, no payer fees

Quantar

Different sectors.One way of working.

Contact

Somethingcomplicated?

Tell us what you're building, where it stands and what you need next. We read every enquiry ourselves and respond within two working days.