Maximus card · build map

Build map

What to code, in what order, and where the USD 20,000 goes. The short version: build the thin layer that makes Maximus yours, and rent everything regulated from partners.

System map

The pilot product in one picture: what exists in the GitHub repo today, what to build next, and what partners provide.

Built in sandboxOn branchBuild nextPartner providesLater

What customers use

Customer appBuild next

Installable web app. The React prototype exists; it needs to show server balances instead of its own.

app/Claude
Owner consoleBuild next

Minimal version for the pilot: cards, limits and activity for the business owner.

app/Claude
Investor demoBuilt

Full simulation at maximus-demo.pages.dev. Doubles as the design reference.

demo/Done

Maximus API (yours)

Login and rolesBuild next

Only a sandbox stand-in exists. Needs phone sign-in, sessions and owner or team roles.

routes/authRoutes.tsCodex
LedgerBuilt

Double-entry and exactly-once, but held in memory. Move it to the database.

services/ledgerService.tsCodex
Mobile money fundingBuilt

Top-up requests and signed provider events, in the sandbox.

routes/paymentRoutes.tsCodex
USDC fundingOn branch

Deposits with source-wallet screening that fails closed. Waiting to be merged.

routes/usdcRoutes.tsClaude
Cards and card spendBuild next

Issue, freeze, limits; payment events debit the ledger. Only the contract exists.

services/providerContracts.tsClaude
Withdraw to mobile moneyBuild next

Money out to the customer's wallet. The route is a placeholder today.

/payroll/disburseCodex
OnboardingBuild next

Thin wrapper around the partner's identity checks. Returns "not configured" today.

routes/onboardingRoutes.tsCodex
Reconciliation and ops viewBuild next

Daily match of our ledger against the partner's records; screen for exceptions.

newCodex
Database · Postgres on your existing Hetzner server. Table designs exist as migrations, not yet connected.backend/migrations/

Partners (rented)

Card programmePartner

Visa card, payment processing, secure card-number display. Onafriq first, Paymentology as fallback.

Mobile money railPartner

Top-ups and withdrawals on MTN, Telecel and AirtelTigo. Often part of the card partner's offer.

USDC providerPartner

Holds the stablecoins and deposit addresses. Rain, Kulipa or Bridge to be asked.

Identity checks and screeningPartner

Ideally included by the card partner. Buying separately is the biggest cost risk.

Build order

Do these in order. Steps 2 to 5 need no partner yet, so coding never waits for contracts.

  1. Merge and add guard rails

    Merge the USDC branch. Add automatic checks so every pull request runs the type checks and tests.

    Done when main has both funding routes and checks run on every pull request.

    Founder · CodexBefore Gate AUSD 0
  2. Database ledger

    Store funding requests, provider events and ledger entries in Postgres instead of memory, using the existing table designs. Every money movement is written in one database transaction.

    Done when a server restart loses nothing and a repeated event still credits once.

    CodexBefore Gate BUSD 0 · existing server
  3. Real login and roles

    Phone number and one-time code, sessions, and owner or team-member roles checked on the server.

    Done when the sandbox login is switched off and every route needs a real session.

    CodexBefore Gate BUSD 0 · SMS costs cents
  4. Cards in the sandbox

    Issue a virtual card, freeze it and set limits. Card payment events debit the ledger and decline when the card is frozen, over its limit or short of funds.

    Done when tests cover an approval and every decline reason.

    ClaudeBefore Gate CUSD 0
  5. App and console on the real API

    Replace the app's own balances with API calls, and build the minimal owner console: cards, limits, activity.

    Done when every balance on screen comes from the server.

    ClaudeBefore Gate CUSD 0
  6. Partner connections

    Swap each sandbox stand-in for the chosen partner: card programme, mobile money, USDC and identity checks. The provider contracts already define the slots.

    Done when the full flow passes in the partner's sandbox.

    Codex · ClaudeGate CPartner fees, see below
  7. Withdraw to mobile money

    Move money from Maximus to the customer's MoMo wallet through the partner.

    Done when a payout settles once and a failed payout puts the money back.

    CodexGate CUSD 0
  8. Reconciliation and ops view

    A daily job compares our ledger with the partner's records. One screen shows mismatches, identity-check cases and support requests.

    Done when a deliberately planted mismatch is caught and shown.

    CodexBefore Gate DUSD 0
  9. Hardening and security test

    Rate limits, a tamper-proof audit log, monitoring and alerts, backups with a tested restore. Then an independent security test.

    Done when no critical or high findings remain open.

    Codex · Claude · testerGate DUSD 2,000

Not now

Each of these is tempting and each would eat the budget or the calendar before the pilot.

  • Native iOS and Android appsUse the installable web app for the pilot. The app stores ask for licensed-partner proof anyway.
  • Physical cardsAfter the pilot. Printing and delivery add cost and weeks.
  • Own identity checks or wallet screeningRent them from the partner.
  • Holding crypto or card numbers yourselfThis is what pulls a company into licences and heavy card-security rules.
  • Bulk payroll and approval chainsBuild them once pilot businesses ask. The demo already shows the design.
  • Rewards, credit, other countriesAfter Gate E.

Who does what

Keep each agent on its own part so they don't overwrite each other.

  • FounderDecide scope, talk to partners and the lawyer, try every change before it is merged, and be the first pilot user.
  • CodexThe backend core: database, login, withdrawals, reconciliation, onboarding.
  • ClaudeCards and card spend, the app and console on the API, tests, and reviewing Codex's pull requests.

How each piece of work moves

The same loop for every step above. GitHub is the single source of truth.

  1. Pick one step from the build order.
  2. The agent works on its own branch.
  3. Tests pass and the other agent reviews.
  4. The founder tries it in the sandbox.
  5. Merge to main and tick it off the roadmap.

Where the USD 20,000 goes

Estimates until the quotes arrive at Gate A. Coding itself costs no cash.

Spending cap by gate

Never pass the cap before the gate is cleared. If a gate fails, at most that much is gone.

GateSpent onCap, USD
A · Quotes in handTrademark search, domain, lawyer's scoping call1,000
B · Partners chosenLawyer's written opinion, partner onboarding fee5,000
C · Sandbox flow worksFirst partner monthly fees8,000
D · Cleared for pilotSecurity test, final legal work, more monthly fees14,000
E · Pilot provenPrefunded card balance18,000

Caps are cumulative. The last USD 2,000 is the reserve.

What costs nothing

  • All the codeCodex and Claude build it. No developer salaries.
  • HostingAPI and database on your existing Hetzner server until the pilot proves out.
  • Automatic testsGitHub's free allowance runs them on every pull request.
  • App store feesSkipped by using the installable web app for the pilot.