Fieldnote is a scheduling and dispatch tool for field service technicians — plumbers, electricians, HVAC crews — replacing paper job sheets and group texts. The founders had already validated demand through pilot customers, but had no engineering team and a seed round that wouldn't close without a working product. We scoped, built, and shipped an MVP in nine weeks, then kept building alongside them as usage data replaced guesswork.
Fieldnote's founders had a validated idea but no engineering team, and needed to prove product-market fit before their seed round closed.
Without a working product, Fieldnote's seed round would close on a pitch deck and a promise — a much harder story to tell investors than real technicians using real software every day.
Usage-based SaaS subscription, priced per active technician seat, sold directly to small and mid-size field service companies.
Field service management software for trades — plumbing, electrical, HVAC — a category historically served by paper processes or generic scheduling tools not built for on-site, mobile-first work.
None — Fieldnote's founders had validated the idea through pilot customers using spreadsheets and group texts, with no existing codebase or engineering team.
A handful of well-funded competitors already served larger field service companies, but none had a mobile-first product built for small, independent crews — the gap Fieldnote was targeting.
Sat in on dispatch calls with two existing pilot customers to see which parts of their paper-based workflow actually broke down under pressure.
Mapped the full technician day — from morning dispatch to end-of-day job notes — to find the three moments that mattered most to prove value.
Evaluated whether a single Next.js codebase with a React Native app could realistically ship both a dispatcher web view and a technician mobile app in the time available.
Scope to three core workflows: schedule, dispatch, complete-and-invoice.
Reasoning
These were the moments investors and pilot customers both cared about seeing work, not a feature checklist.
Trade-off
Left out route optimization and inventory tracking, both of which pilot customers asked for early.
Ship a mobile web app first, native later.
Reasoning
A responsive web app could reach technicians on day one without app store review delays.
Trade-off
Early users lost offline support and push notifications until the native app followed a few weeks later.
Instrument every core action from day one.
Reasoning
Real usage data, not opinions, needed to drive the roadmap once the MVP was live.
Trade-off
Added a week of engineering time the founders initially wanted to spend on more workflows.
Technician Web App (Next.js)
Next.jsA mobile-responsive web app technicians use in the field — schedule, job details, and completion in one flow.
More on Next.js in the Technology ExplorerWhat happened
Technicians worked in areas with unreliable cell coverage, and the initial web-only MVP had no offline support.
How we resolved it
Added optimistic UI updates that queued actions locally and synced once connectivity returned, buying time until the native app's real offline mode shipped.
What happened
Job-completion photos were large enough to slow uploads on cellular connections.
How we resolved it
Added client-side image compression before upload, cutting typical upload time significantly on slow connections.
Approach
We scoped an MVP to the three workflows investors cared about most and instrumented it from day one, so real usage data — not guesses — drove the roadmap after launch.
Outcome
Fieldnote closed its seed round two months after launch, backed by real usage data instead of a pitch deck alone.
Weekly active technicians
Time to MVP
Time to seed round close
“We closed our seed round eight weeks after launch, backed by real usage data instead of a pitch deck alone. Scoping to three workflows instead of everything on our wishlist is the reason we shipped in nine weeks at all.”
Priya Nair
Co-Founder & CEO, Fieldnote
Route optimization for technicians handling multiple jobs in a day
Client planBuilt-in invoicing and payments, currently handled outside the product
Client planA configurable workflow builder so the product could serve trade types beyond the initial three
Byld IQ recommendationBuildPath turns your version of this problem into a personalized roadmap in about three minutes — or talk to Byld first if you still have questions.