Wire the core flow to real data
- Impact
- Pilots expose placeholder data. Trust breaks on day one.
- Do
- Connect save/load on the one path that matters.
FieldDesk MVP Review
What a review looks like for an AI-built B2B product: verdict, ranked fixes, and a brief to implement.
Quick read
Skim this first. The detail is below if you need it.
Verdict
Looks finished in demo. Core flow is not wired, and new users are lost on first open.
Blockers
- Demo data, not real saves
- No first-use orientation
- Setup does not connect to product
- Prompt creep: competing CTAs
Do next
Ship the top 4 fixes. Run three walkthroughs with someone who has never seen it.
Top 4 fixes
The four issues we see in almost every vibe-coded MVP.
Explain what this is on first open
- Impact
- Demos stall when users cannot tell what it is for.
- Do
- One-line value + one obvious first action.
Connect setup to the first real screen
- Impact
- Users finish onboarding and land somewhere that ignores what they entered.
- Do
- Pass saved inputs forward; confirm what carried over.
Cut prompt creep on every screen
- Impact
- Each iteration added another equal-weight CTA. Users stall.
- Do
- One primary button; demote or remove the rest.
Issues
One line each. Expand for next steps.
#1
Demo data, not real saves
UI looks finished, but core flow still runs on placeholders or hardcoded values.
High
Demo data, not real saves
UI looks finished, but core flow still runs on placeholders or hardcoded values.
Next steps
- Pick one path that must work for a pilot; wire save and load end to end.
- Replace sample rows and fake success states with real persisted data.
#2
No first-use orientation
Users land on setup or an empty dashboard with no context.
High
No first-use orientation
Users land on setup or an empty dashboard with no context.
Next steps
- Value line above config; one primary action before empty states.
- Defer branding until after the first meaningful action.
#3
Setup does not connect to product
Each screen was a separate prompt. Onboarding never feeds the main app.
High
Setup does not connect to product
Each screen was a separate prompt. Onboarding never feeds the main app.
Next steps
- Pass onboarding output into the first meaningful screen.
- Welcome recap confirming what was saved.
#4
Prompt creep: competing actions
Each vibe iteration added another equal-weight button or feature.
High
Prompt creep: competing actions
Each vibe iteration added another equal-weight button or feature.
Next steps
- One primary button per screen; demote or cut the rest.
- Helper text under the primary CTA explaining the outcome.
#5
Save failures fail silently
When Supabase rejects a write, the UI still shows success.
High
Save failures fail silently
When Supabase rejects a write, the UI still shows success.
Next steps
- Handle API errors and show inline failure with retry.
- Disable submit until save confirms; log errors for debugging.
#6
Sample team members in production
"Alex Demo" and "Test User" still appear in assignee lists.
High
Sample team members in production
"Alex Demo" and "Test User" still appear in assignee lists.
Next steps
- Remove seed data from assignee and team pickers.
- Gate team invites behind real auth; empty state until first invite.
#7
Jargon labels
Nav names use metaphors users cannot map to real tasks.
Med
Jargon labels
Nav names use metaphors users cannot map to real tasks.
Next steps
- Rename nav and CTAs to plain task language.
- First-visit helper text under unfamiliar items.
#8
Text-heavy screens
Long AI copy buries the action. Flat hierarchy.
Med
Text-heavy screens
Long AI copy buries the action. Flat hierarchy.
Next steps
- Lead with one line, then two short bullets.
- Collapse long rationale behind "Read more".
#9
Empty states without a next step
Blank job lists and schedules show no guidance on what to do first.
Med
Empty states without a next step
Blank job lists and schedules show no guidance on what to do first.
Next steps
- Replace "No jobs yet" with one primary action and a one-line explanation.
- Show example state or checklist for first-time workspaces.
#10
No loading feedback between steps
Assigning a job or switching views feels instant but data is still fetching.
Med
No loading feedback between steps
Assigning a job or switching views feels instant but data is still fetching.
Next steps
- Add skeleton or spinner on list and detail transitions.
- Disable double-submit on forms until the request resolves.
#11
Filters do not stick
Region and status filters reset on navigation or refresh.
Med
Filters do not stick
Region and status filters reset on navigation or refresh.
Next steps
- Persist filter state to URL params or user preferences.
- Restore filters when returning from job detail.
#12
Mobile job detail breaks layout
Action bar overlaps content; assignee picker clips off screen.
Med
Mobile job detail breaks layout
Action bar overlaps content; assignee picker clips off screen.
Next steps
- Stack action bar below content on narrow viewports.
- Test assign flow at 375px width before pilot.
Agent brief
Paste into Cursor, Lovable, or your coding agent.
Implementation prompt
Click to expandWant this for your product?
Verdict, ranked fixes, issues, and an implementation brief.
View MVP Review offer