Matta

One calm operating system for consultants and their clients.

Matta brings consultant workspaces and client portal actions into one secure product so delivery stays consistent from setup to execution.

HomeClient login

Product foundation

The production app is now online with real deployment, real authentication, and the first live backend wiring in place.

App onlineBackend connected
Consultant app
Live shell

The consultant routes now sit on real auth and live saved setup state.

Auth
Consultant login ready

Consultant onboarding and login are already flowing through the live identity layer.

Data layer
Supabase ready

The real database layer is wired and ready for firms, clients, projects, and workspaces.

Core product surfaces

These are the live product surfaces now taking shape inside the production codebase.

JTBD sprint path

Matta is moving in the launch order that keeps risk low: foundation first, then operational records, then messaging and payments.

Sprint 0: Production setup
Current

Next.js app, GitHub, Vercel, environment structure, and launch decisions.

Sprint 1: Consultant and client auth
Queued

Consultant login, client login, onboarding, and shared backend identity model.

Sprint 2: Backend and data model
Queued

Supabase schema, storage, and core access policies for clients, projects, workspaces, and artifacts.

Sprint 3: Consultant workspace foundation
Queued

Clients, projects, services, settings, and the premium shell of the consultant app.

Sprint 4: Templates and workspace engine
Queued

Service templates, module library, roadmap builder, weighted progress, and workspace snapshots.

Sprint 5: Client portal and operations
Queued

Portal, chat, activity, document threads, forms, invoices, meetings, and one-off workspace items.

Sprint 6: Payments, messaging, and launch hardening
Queued

Paystack, Termii, Resend, QA, security, audit trails, and production rollout.

Where to review next

Use these to move between the consultant and client entry points while the core experience comes online.

Step 1

Consultant auth and consultant onboarding are now running against the live production stack.

Step 2

Supabase is connected, and the first schema foundation is in place for firms, clients, projects, and workspaces.

Step 3

Client access will keep the Nigeria-first Termii path for SMS plus WhatsApp as that layer comes online.

Remaining launch connections

These are the integrations still to be wired as the operational modules come online.

Clerk publishable key and secret key
Google OAuth client ID and secret
Supabase URL, anon key, and service role key
Resend API key and sending domain
Termii API key, base URL, and approved messaging channels
Paystack public key, secret key, and webhook secret