LevrAge.Innovation Studios
← Back to the studio

The studio / Work & experiments

Built, explored
and learned from.

Community platforms, client builds, studio products and earlier experiments. Each has its own stage; a running demo alone does not establish adoption or production readiness.

Shipped & maintained

Community work

Live platforms built for community organizations — deployed, maintained, and separate from client MVPs and lab experiments below.

Live · maintained

Association of Zambians in California

Built and deployed for the ZANC community — events, membership, and payments on a site the association owns and runs day to day.

  • Vite + React + Supabase: content, dues, and community workflows.
  • Live and maintained — not a client MVP or experiment.
Live · maintained

NorCal → Zambia community shipping pools

Studio-built MVP for Operation iDream — pledge container space, watch fill levels hit goal, ship when the community threshold is reached.

  • Pledge-first model: no payment until the pool is confirmed and announced.
  • Live on Vercel with container thermometer, pricing, and admin flows.

In-house products

Studio flagships

Built and owned at LevrAge Innovation Studios — at different stages, and labeled that way: live products, working MVPs, and early concepts. The same patterns we bring to client work.

Live

Verifiable AI + data infrastructure — the studio's long arc.

The studio's long-horizon venture: trust and verification infrastructure for AI and data workloads, currently in deep R&D.

What we shipped

  • Core data and infra patterns that support AI-augmented workflows.
  • The engineering discipline behind it (receipts, audit trails) shows up in client builds today.
Live

Zambia market-entry strategy & intelligence

Strategy surface for investors and diaspora looking at Zambia — sector notes and market-entry frameworks that pair with the studio's build capacity.

What we shipped

  • Corridor and sector research notes for Zambia market entry.
  • Pairs with ZambiaMacro signals and studio build work.
LevrAge example card in the Prism edition: the sample name Alex Morgan beside a line-drawn holographic ring.
Example card · levrage.app
Live

A card worth showing.

The studio's own product. Make your card, share it with a scan, and let Levi help you remember the people you meet. Live, with open beta in preparation.

What we shipped

  • One card drives its face, its QR code and its contact file. The QR carries only the fields you choose, and sharing by scan needs no account.
  • Tell Levi who you met, by voice or text, and it saves the person with the context.
  • Released 30 October 2026 after 862 automated tests and 19 read-only production checks.
Live

Lobito Corridor trust layer (concept)

Early concept for a trust layer on Africa's Atlantic export corridor — an exploratory build sharing patterns with CopperCloud, not an operating platform.

What we shipped

  • Next.js + Firebase with Pinecone-backed intelligence for corridor workflows.
  • Parked until the corridor work has a real audience.
Live

The history you were never taught

Narrative archive experiment for Zambia's untold stories — dormant, kept for future public-history work.

What we shipped

  • Next.js + Three.js narrative experiences over a Supabase-backed archive.
Live

Community emergency mobilizer

Early-stage mobile concept for community emergency response — designed and prototyped, not in active development.

What we shipped

  • Event-driven flow to request help and notify vetted drivers.
  • Location and destination logic oriented around local hospitals and services.

Early-stage Flutter concept · studio-owned

Client delivery

Selected client MVPs

Shown with permission — execution patterns and shipped scope, not proprietary product ideas.

Alpha01 (telehealth MVP)

Problem

A health organization needed a secure way to deliver telehealth services and manage patient interactions in a specific regional context.

Solution

Specialized telehealth MVP with secure access, visit flows, and provider–patient communication primitives.

What we shipped

  • Auth and role-based access for patients and providers.
  • Telehealth-ready flows that can be extended into full EHR or integrations.

EDC Consulting

Problem

A consulting practice needed a credible bilingual web presence with clear service positioning.

Solution

Marketing site with dynamic placeholders and share-ready Open Graph metadata.

What we shipped

  • Bilingual content structure for English and French audiences.
  • Lightweight deployment suitable for ongoing content updates.

PBS (Phoenix Bookkeeping)

Problem

A bookkeeping firm needed a simple, credible web presence and light operational tooling.

Solution

Small business MVP that communicates services and supports basic client workflows.

What we shipped

  • Service site with structured information architecture.
  • Simple flows that can evolve into client onboarding or portals.

The Wealth Shift

Problem

A wealth and finance brand needed a clear online presence that could educate and convert without a complex app.

Solution

Brand and funnel site that explains the offer, captures leads, and guides visitors into the right next step.

What we shipped

  • Conversion-oriented marketing site with clear narrative and CTAs.
  • Lightweight infrastructure that can later plug into more advanced tools.

Studio research / Platform R&D

Platform infrastructure

The deepest systems we build and run in-house: signed receipts, audit trails, and governed data pipelines. These are working R&D platforms that show our engineering discipline — shown honestly as research builds, not commercial products.

In-house R&D platform

Proof-carrying compute (R&D)

Working R&D platform for verifiable computation — receipts, attestation, and workload coordination, run on our own nodes as an engineering proof.

  • • Ed25519-signed receipts, hash-chained audit trail, capability-aware workload routing.
  • • 453 automated tests and a hash-chain-valid daily receipt run — deep build discipline, no external operators yet.
CopperCloud orchestrator (R&D demo) →

In-house R&D platform

Zambia Power Stress Index

A public monitor of power stress in Zambia's Kariba hydrology channel, built from public data. Readings are labelled observed or estimated, with the model's confidence shown: a present-state reading, not a forecast.

  • • Collects public hydrology, rainfall, exchange-rate and copper-price data on a daily schedule.
  • • Publication is gated by data freshness, and the page states the model's limits, including the range of scores it can reach.
  • • Days without a reading are left blank, not filled in.
zambiamacro.ai →

Partner work / Institutional

Institutional products

Evidence and traceability systems built with partners — each shown at its actual stage, because that's how we work.

Partner build · Live

RISE Evidence Engine

Zambia-first evidence infrastructure. Development decisions that can be traced, trusted, and improved. Phase 2 in progress.

  • • FastAPI ingest + Vite/React dashboard with district-level artifacts, CDF-aware views, and audit-grade provenance.
  • • CopperCloud receipt integration for collector runs — live at risegrow.org, Phase 2 in progress.
  • • Built for institutional partners and field validation workflows, not a client marketing site.

Exploratory

Labs & experiments

Project ideas and early builds — some shipped as demos, most started for clients or partners who didn't move forward. Not maintained like community work above.

Afriai

Demo / paused

Early concept at the intersection of African markets and AI infrastructure — pattern tests, not a maintained product.

View build →

RefridgeX

Demo / paused

Cold-chain and inventory experiment — client scaffolding that did not move into active delivery.

View build →
  • Pantry

    Shopping assistant concept for busy parents — voice, text, and links into store lists. Idea-stage build.

  • Tenat

    Property management prototype — started for a client who did not push forward.

  • ChaloSpace

    Earlier property-management iteration — archived experiment, not maintained.

Engineering / Working principles

How we think about systems

Every MVP needs infrastructure decisions. Here's how we approach them at the studio.

Select a component to highlight it. Every explanation is available above.

Discuss your own task →