Before You Build
English
English中文日本語
Web AppShut Down

College Conductor

College Conductor targeted a narrow education workflow with an apparent close-at-hand first user. The founder later said he lost that user before delivering enough value, while stack complexity and package maintenance displaced customer development.

View original story

Product snapshot

What it was

College Conductor was a side-project SaaS for independent education consultants and college counselors to track students, schools, applications, and deadlines.

Who it was for

independent education consultantscollege counselors

Problem / value

Centralize student and school-application tracking so counseling workflow management felt less clunky.

Core workflow

Counselors tracked students, colleges, application deadlines, and admissions details from one workflow.

Product form

web appopen source repository

Pricing model

No public pricing data found in the sources used.

Competitors or alternatives

existing online tools for independent education consultantsspreadsheets and manual counselor workflowsvertical CRM/workflow tools for education consultants

What happened

Summary

The founder says College Conductor was shut down after three years of running the SaaS.

Core risk

Overbuilt Stack And Slow Customer Validation

Timeline

  • The founder ran the SaaS effort for three years before shutting it down.
  • The founder later used the project as teaching material for Django SaaS development streams.
  • The public GitHub repository shows College Conductor as a side project / experiment.

Before you build

Why it matters

College Conductor targeted a narrow education workflow with an apparent close-at-hand first user. The pre-build question is whether independent education consultants and college counselors have enough urgency, budget, and repeat behavior to support this workflow through a channel you can keep reaching.

Primary check

Deliver a narrow counselor workflow to one committed user before investing in stack complexity or broad product scope.

Checklist

  • Who owns the budget for this problem?
  • What repeated event triggers the buyer to use this every week or month?
  • Which channel reliably reaches independent education consultants and college counselors without a one-off launch spike?
  • What evidence would show Overbuilt Stack and Slow Customer Validation before you build more?
  • Define which segment among independent education consultants and college counselors pays first and why the problem is urgent now.
  • Prove the workflow happens often enough to justify buying.
  • Test one acquisition channel for independent education consultants and college counselors before relying on launch traffic.
  • Write down why a buyer would switch from existing online tools for independent education consultants, spreadsheets and manual counselor workflows, and vertical CRM/workflow tools for education consultants.

Relevant if

  • You are building a web app for independent education consultants and college counselors.
  • The product promise is specific: Centralize student and school-application tracking so counseling workflow management felt less clunky.
  • You have interest, signups, usage, or founder confidence but have not proven paid repeat use.
  • Buyers can already use existing online tools for independent education consultants, spreadsheets and manual counselor workflows, and vertical CRM/workflow tools for education consultants or avoid switching altogether.

Less relevant if

  • You already have paying independent education consultants and college counselors who repeatedly use the workflow and renew or expand usage.
  • The product is an internal tool with a mandated user base and no external go-to-market risk.

Pre-build tests

  • Run the workflow manually for a small group of independent education consultants and college counselors.
  • Ask one buyer to pay, renew, or sign a dated pilot before building the next version.
  • Test one non-launch acquisition channel and count qualified conversations, not page views.
  • Put the offer next to existing online tools for independent education consultants, spreadsheets and manual counselor workflows, and vertical CRM/workflow tools for education consultants and ask what would make the buyer switch now.

Transferable lessons

  • A narrow vertical does not remove the need for repeated customer development.
  • Unfamiliar frontend and deployment choices can consume the limited energy a solo founder needs for customer learning.
  • For a first SaaS, the fastest path to a useful customer workflow is usually more valuable than a technically ambitious stack.