Pipeline board
Drag each firm through Networking → Applied → Interview → Offer. Each stage auto-stamps its date and unlocks its own section on the firm - interview rounds, offer details with a respond-by deadline, or a post-mortem takeaway.
Private by design · built for students
Pipeline
Your whole recruiting season, in one place.
Nothing forgotten
Nothing double-entered
Everything in sync
01
The Problem
Recruiting is a logistics problem disguised as a networking problem.
Most students track it in a spreadsheet that goes stale, a Notion page they stop updating, or their memory. The cost of a dropped thread - a missed deadline, a contact who went cold, a chat they forgot to log - is measured in lost interviews and offers.
- 20+ firms to track, each with its own open date, close date, and stage.
- Dozens of contacts - recruiters, alumni, interviewers - and remembering who to follow up with, and when.
- A timeline where firms open and close on staggered, rolling schedules.
- Coffee chats and calls, frequently arranged ad hoc over text.
Networking
Applied
Interview
Offer
Drag a firm through its stages and the app stamps the date you hit each one - your pipeline history writes itself. One date or chat shows up on the firm, the calendar, the outlook graph, and your own synced calendar. Never entered twice.
02
The Approach
Pipeline replaces the scattered mix of spreadsheets, sticky notes, and school portals with one personal system - faster than a spreadsheet, smarter than memory. It's designed around a single idea: recording your history should happen as a side effect of the actions you were already taking.
The organized path is the easy path
History is a side effect of a drag or a log - never extra data entry.
Keep the record honest
Plans and records stay separate; nothing counts as done until you confirm it.
One entry, many views
A single date appears everywhere it's useful, entered exactly once.
Actionable over informational
The dashboard answers "what needs me now?", not "how many things exist?"
03
Capabilities
Every feature earns its place by serving the core loop - track firms, nurture contacts, never miss a date.
Application outlook
Every firm's open→close window drawn as a bar, sorted by open date and colored by stage, with markers for each milestone you've hit. The whole season at a glance.
Contacts as the real pipeline
Recruiters, alumni, and interviewers grouped by firm. Every logged touch advances your follow-up date, and naming an interviewer adds them as a contact automatically - relationships build themselves.
Scheduled chats
Book the chat, keep its join link and running notes on one card, and log it right there when it's done - sentiment, referrals, next step. Nothing counts as "contacted" until you confirm it happened.
Calendar sync
A one-click feed pushes deadlines, follow-ups, and timed chats into Google, Apple, or Outlook - so native notifications do the "don't miss it" work. Outbound only; the app never reads your calendar.
A dashboard that watches for you
Firms closing soon, overdue follow-ups, chats waiting to be logged, offer responses coming due - every tile answers "what needs me now?" and takes you straight there.
Ask Pipeline
Ask in plain language - "what needs my attention?", "which firms have I interviewed with?", "when do I respond to my offer?" - and get instant, deep-linked answers. Runs entirely on your device: no model calls, nothing leaves it.
04
Decisions & Tradeoffs
Every significant feature started as a written spec - problem, options, chosen approach, tradeoffs. A few of the decisions that shaped the product:
Architecture
Plan vs. record
- Decision
- A future chat lives in its own table and only becomes a logged interaction when you confirm it happened.
- Why
- Writing a booked-but-unheld meeting into the log would prematurely mark a contact "contacted" and advance the follow-up clock - wrong the moment it's cancelled.
Product
Actionable, not informational
- Decision
- The dashboard's three tiles are active firms, firms closing soon you haven't applied to, and overdue follow-ups - not passive counts.
- Why
- Each tile answers "what needs my attention now?" and points somewhere different, turning the dashboard into a to-do surface rather than a status readout.
Architecture
Isolation at the database
- Decision
- Managed Postgres with Row-Level Security on every table, rather than a custom server.
- Why
- Isolation is enforced at the database with per-user policies - not trusted to the client. New signups start with a genuinely blank slate.
05
Get Early Access
Be first in line when Pipeline launches.
The app is feature-complete and heading for deployment. Drop your email and I'll let you know the moment it's live - no spam, just the launch note.
You're on the list - talk soon.
That didn't go through. Check your connection and try again.
Private per user, with data isolation enforced at the database.