UX/UI Design • Product Strategy • Architecture Design
Lead Management: From Purpose-Built Tool to SaaS Platform
How a purpose-built intake system became a SaaS product serving eighteen clients — with one engineer and no product team.
The Origin
40,000 Submissions. One Excel Spreadsheet.
In January 2025, a destination golf client came to Noteefy with an unusual logistics problem. Once a year, they'd release their entire booking availability in a single drop. Within an hour, they'd receive upward of 40,000 submissions — and their team would work through them on a first-come, first-served basis out of a spreadsheet.
We built them a tool. It worked. Then we asked a hard question: what would it take to make this a product?
The Strategic Decision
A Tool Solves One Problem for One Client. A Product Solves Many Problems for Many Clients.
The purpose-built version had a single form, a single client, and a single workflow. Converting it to a platform meant decoupling everything — form creation, lead intake, communication, permissions, configuration — and rebuilding each layer for flexibility rather than just function.
The first application of Component Methodology here was to the form system itself. We'd built it internally for one client's schema. That wasn't scalable. We white-labeled Feathery as a form builder, offloaded configuration to the client, and our system became the hub. One decision eliminated an entire category of future custom work.
The Roadmap
A Compass, Not a Map.
With one engineer and no dedicated product team, the roadmap had to be honest about what we didn't know. I structured it in three phases. Not because I knew exactly what each would contain, but because I knew the shape of the journey.
The details under each phase have shifted as the market dictated. The core concepts, however, haven't moved.
Phase 1
Complete
Enterprise Basics
The minimum required to be taken seriously. Analytics, lead management, roles and permissions, communication integrations. Not to win deals — to establish the baseline for evaluating product-market fit.
Phase 2
In progress
Differentiator
One thing none of our competitors can easily build. Our moat is specificity — the golf industry is a footnote in Salesforce’s roadmap. That gap is ours to fill with data and a client-facing guest portal.
Phase 3
Next
Expansion
Deliberately underspecified. New verticals, higher ACV, expanded product offerings. The decisions here only become clear once Phase 1 and 2 tell us something real.
Know where you're going before you leave the driveway.
A roadmap isn't a list of every turn between here and the destination, it's a compass. When we start, it provides us a general direction to go. As we get closer to our destination, the reading becomes more precise. Instead of needing the exact route, we just follow the compass at the beginning, and the route will become more clear the closer we get.
It's important to know your destination so you know your travel options. If I'm heading from Boston to California, I can drive. But if I'm heading to Hawaii, I don't want to find out I can't drive there after I make it to the California coast. In both cases we go West, but having an understanding of the destination (even a general one) is valuable in ensuring we embark on the right path with the right tools. A generalized and phase-based roadmap gives direction without false precision. The closer you get, the more the route reveals itself.
The Execution
I Don't Build a Prioritization. I Discover One.
Defining Enterprise Basics started with a question: what would it take to call this finished? Full lead management in one place, reporting and analytics, and a permissions system robust enough for real organizational structures. Once I had that picture, I worked backwards.
If I need the Outlook integration, what has to be true first? Async communication only makes sense if agents are already handling phone intake. Phone intake only makes sense if lead records are editable. Editable records only make sense if there are enough leads in the system to justify the workflow — which means multi-form infrastructure comes first. Each dependency pointed to the next. The sequence didn't come from a planning session; it emerged from the end state.
01
Multi-Form Infrastructure
Specialized intake forms for any use case. Multiple entry points, one unified record.
↓
More leads in the system → closer to system of record
02
Phone Intake
Call leads close at a higher rate. The system needed to support both channels to capture the full picture.
↓
Agents working leads need to update records in real time
03
Lead Editing
Form data comes in through a third-party system. Maintaining the edit inside Noteefy required mapping schema and building custom sync — but the alternative was agents working with stale records.
↓
Inbound calls require fast lookup before a new record is created
04
Quick Lookup
As data is entered during a call, the system surfaces existing records in real time. Prevents duplicates before they happen.
↓
If we’re managing calls, we need to manage written communication too
05
Outlook Integration
Outbound emails triggered from within the system, associated to the lead automatically. Every interaction — email, call, status change — logged to a single record.
Governance Layer
Define the Roles Once. Let the Definitions Answer the Questions You Haven't Asked Yet.
Most organizations handle permissions feature by feature — every release becomes a conversation about who gets access to what. I'd rather answer that question once, at the system level, than answer it forever in meetings.
We defined three roles by the job they do, not by the features they touch. Agents work individual leads. Managers support the agents who work leads. Admins configure the system those agents and managers use. Every feature we've built since maps cleanly to one of those definitions. The roles don't just manage access — they eliminate a recurring decision.
This is design systems thinking applied to organizational governance — the same instinct that makes a component library valuable. Invest in the definition early, and it compounds forward.
The Outcome
Two Builders. Six Months. The Top Courses in the world. 6× Client Growth.
We launched with three clients. Six months later, that number is eighteen, with 52 courses under management across those properties. The clients who have chosen the platform include courses ranked among Golf Digest's World's 100 Greatest and America's 100 Greatest Public Courses, most of which were not Noteefy clients until the Lead Management product..
This was built by two people: one designer functioning as product manager (that's me!), and one engineer, who was pulled to other priorities throughout. No product team, no dedicated QA, no design system handed down from above. The constraint wasn't a limitation to work around; it was the condition that made every decision matter.
6×
Client growth since launch
52
Courses under management across 18 clients
Top 10
Client courses rank among Golf Digest’s World’s 100 Greatest
6+
Client courses ranked on Golf Digest’s America’s 100 Greatest Public
Component Methodology in Action
A Single Client Request Unlocked Three New Features.
A current client needed to randomize prioritization for a high-demand booking window. The instinct would be to build a lottery system.
Instead, we asked the Component Methodology questions first. The lottery requires weighted scoring — structurally identical to lead scoring we'd been holding. It requires a rules engine; the same infrastructure needed for automated lead routing. And the outcome triggers a workflow which maps directly to lead tagging we'd already planned.
We didn't build a lottery system. We built tagging, a rules engine, and a scoring framework. The client's custom request became a platform-wide release.
Client asked for
Lottery System
Component Methodology reframed the request as reusable product logic, not a one-off feature.
↓
Weighted scoring
Run the lottery with weighted criteria instead of random selection.
Configurable rules
Lottery configuration needed rule logic that could be reused beyond the first ask.
Winner / loser workflow
Determining outcomes created the need for a lightweight automation path.
↓
Unlocked
Lead Scoring
Unlocked
Auto Lead Routing
Unlocked
Automated Workflows + Lead Tagging
