All Work
Product BuildAI mentorship

MNTR

An AI mentorship and strategy platform for storytellers and founders — chat, playbooks, courses and a mission system, built around getting someone to say what they are actually trying to build.

MNTR — Plan selection — credits, not seats, as the unit of value. Captured from the running app.
Plan selection — credits, not seats, as the unit of value. Captured from the running app.

The problem

Mentorship does not scale, and every attempt to scale it dilutes the thing that made it work. A good mentor's value is not information — it is the questions they ask and the judgement behind them.

MNTR is an attempt to encode that: AI chat, playbooks, structured courses and a mission system, all shaped around a particular expert's way of thinking rather than around generic advice.

Asking a better first question

The onboarding does not ask for a job title or a company size. It asks, by name: what are you actually building toward — not the safe answer, the real one, the one that keeps you up at night. And it offers a graceful way out: "Not yet — I'll come back to this."

That is the whole product's thesis compressed into one screen. A mentorship tool that opens with a form is going to get form answers, and form answers are exactly what makes generic advice generic. The escape hatch matters as much as the question — pressuring someone into a half-honest answer would poison everything downstream of it.

Colour doing one job

The palette is a single signal green on near-black, with a warm off-white for light surfaces. The brand is parameterised as one variable — --brand-hue: 145 — and the rest of the system derives from it.

Restricting the palette to one accent means green always means the same thing: this is the action. On a dark ground with a hundred screens to keep coherent, that consistency is worth more than a wider palette would be.

Under the interface

A hundred screens sit on an Express and PostgreSQL back end — three hundred and thirty-five server files and a hundred and forty-two migrations, with Drizzle holding the schema and a hundred and ninety-three tests holding the behaviour.

The AI is not one model. Gemini and Perplexity do different jobs — reasoning and retrieval — while Stripe meters the credits that are the product's unit of value rather than the seats, and Twilio carries the parts of the mentorship that happen off the platform.

Palette

Primary

#00C753

Signal green — every action

Foreground

#171717

Near-black

Background

#F8F8F7

Warm off-white, light mode

Card

#FAFAF9

Barely lifted from the ground

Border

#E7E7E4

Warm hairline

Scope

Screens
100
Components
167
Server files
335
Migrations
142
Tests
193

Screens

MNTR — The opening question — personalised, deliberately uncomfortable, and easy to defer.
The opening question — personalised, deliberately uncomfortable, and easy to defer.
MNTR — The Growth Audit walkthrough, step one of four.
The Growth Audit walkthrough, step one of four.

What we did

  • Product design
  • Interface design — 100 screens
  • Onboarding and conversion flows
  • Full-stack build
  • AI integration

Built with

  • React
  • TypeScript
  • Vite
  • Tailwind
  • shadcn/ui
  • Express
  • PostgreSQL
  • Drizzle ORM
  • Gemini
  • Perplexity
  • Stripe
  • Twilio