Case study · build journal

The thinking behind the build.

Pipeline keeps the chaos of recruiting in one place - firms, contacts, deadlines, and coffee chats. Here is what it is, the problem it solves, and how it came together.

01

What It Is

Pipeline is a web app that keeps the chaos of recruiting in one place: the firms you're applying to, the people you're networking with, the deadlines you can't miss, and the coffee chats you've lined up. It's built for college business students recruiting for consulting, finance, and adjacent roles.

It is private to each user, and designed to replace the scattered mix of spreadsheets, sticky notes, and school portals that students juggle during recruiting season.

02

The Problem

Recruiting is a logistics problem disguised as a networking problem. At the same time, a student is usually:

  • Tracking a long list of firms, each with its own timeline and stage
  • Managing a web of contacts - recruiters, alumni, interviewers - and remembering who to follow up with, and when
  • Juggling deadlines that open and close on staggered, often rolling schedules
  • Arranging coffee chats and calls, frequently set up ad hoc over text

Most students hold all of this in a spreadsheet that goes stale, a doc they stop updating, a portal that only covers postings, 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.

Recruiting is a logistics problem disguised as a networking problem.
Pipeline exists to make the organized path the easy path.
03

How It's Built

A modern, typed web app over a managed database - built to be fast, private, and low-maintenance.

A typed front end. Pipeline is a single-page web app with two hand-built themes - a dark "Midnight slate" and a light "Paper & ink" - and a typographic identity of its own. The pipeline board is fully drag-and-drop, and the interface is tuned to load quickly and stay responsive.

A managed, private back end. Data lives in a managed database with per-user isolation enforced at the database itself, so each person can only ever see their own pipeline. There is no custom server to run or secure. A couple of lightweight background jobs power the outbound calendar feed and email reminders.

Built around a clear model. Firms, contacts, interactions, and planned chats each have a well-defined role, and the app keeps a deliberate line between what is planned and what has actually happened - the detail that keeps the follow-up logic honest.

04

The Features

Every feature earns its place by serving the core loop - track firms, nurture contacts, never miss a date.

Pipeline board

Every firm is a chip you drag through your recruiting stages. Each stage records its date and unlocks its own section on the firm - interview rounds, offer details, or a post-mortem takeaway - as a side effect of the move you were already making.

Firms with real dates

Each firm carries its open and close dates, which then show up wherever they're useful - on the firm, on the calendar, and in your synced personal calendar. One entry, many views.

Contacts as the real pipeline

Recruiters, alumni, and interviewers grouped by firm. Logging a touch keeps "last contacted" current and nudges the next follow-up - and naming an interviewer on a firm adds them to your contacts automatically.

Scheduled chats

A coffee chat arranged over text becomes a card holding the plan, the join link, and your running notes. Once it's passed, it quietly nudges you to log what happened - sentiment, referrals, and the next step.

Calendar & application outlook

A month view of deadlines, follow-ups, and chats, plus a season-long timeline of every firm's window - so you can see the whole stretch, and where you stand in it, at a glance.

Calendar sync

A one-click feed pushes your deadlines, follow-ups, and chats into Google, Apple, or Outlook, so the calendar you already live in does the "don't miss it" work.

A dashboard that watches for you

At-a-glance tiles that surface what needs you now - deadlines closing in, follow-ups that have slipped, chats waiting to be logged, and offer responses coming due - alongside a snapshot of your whole pipeline.

Ask Pipeline

Ask in plain language - "what needs my attention this week?", "who am I overdue with?" - and get an instant, deep-linked answer. It runs entirely on your device, so nothing ever leaves it.

05

The Build Journey

Spun off from a larger personal project into a standalone, focused app. The rough arc it followed:

  1. Foundation
    The data model and per-user privacy, with isolation built in from the very first step.
  2. From one screen to an app
    A move from a single dashboard into a real multi-screen app: a firms directory and board, a full calendar, and a nav shell that works on both desktop and mobile.
  3. Dates & follow-up automation
    Application windows and a follow-up rhythm that advances on its own without ever overriding a date you set deliberately.
  4. Scheduled chats
    A way to plan a coffee chat, keep it separate from the record until it happens, and have it sync cleanly to your calendar.
  5. Outlook & a sharper dashboard
    A season-long timeline view and a dashboard reframed around what actually needs your attention.

Each meaningful feature started as a short written plan before any code, and was built in small, reviewable steps.

06

Design Principles

The organized path is the easy path
Recording history happens as a side effect of normal actions, not as extra data entry.
Keep the record honest
Plans and records stay separate; nothing counts as "done" until you confirm it. This protects the follow-up logic that is the point of the tracker.
One entry, many views
A single date or chat shows up wherever it's useful - never entered twice.
Actionable over informational
The numbers answer "what needs me now?", not "how many things exist?"
Private by design
Each user's data is isolated at the database, not trusted to the client.
07

Data & Privacy

A user's pipeline is theirs alone
Every user's data is isolated at the database and visible only to them. A new account starts with a completely blank slate - nothing is seeded and nothing is shared. Privacy isn't a setting here; it's how the app is built.

Read the decisions behind the build.

See the product and engineering calls that shaped Pipeline - what was chosen, why, and what was traded away.