25d • General discussion
Pilot customer Pay vs Free
Hey guys wonder if you can give me some advice please. So I am looking at a pilot customer who initially I thought free forever (my thought was then I don't have to look for another pilot) however after a few discussions it came up that I should still add structure to add value for both parties so came up with this, can you comment please
🟢 Level 1 – Concept (Free)
- Diagnostic
- High-level workflow sketch (“concept of the fix”).
- ROI framing (what the leak is costing).
- Purpose: Show value
🟡 Level 2 – Design (Low-Cost) ('MVP')
- Detailed workflow design (how the automation will work).
- System mapping + tool integration plan.
- Quote/proposal for implementation.
- Purpose: Paid planning stage — proves seriousness.
🔵 Level 3 – Implementation (Core Paid)
- Build the automation
- Test + integrate with client’s existing systems
- Deliver functional solution.
- Purpose: Main delivery tier — visible ROI.
🔴 Level 4 – Maintenance (Ongoing Retainer) (I was thinking of making this free for the Pilot customer)
- Monitor, patch, and optimize automations.
- Add upgrades as business grows.
- Support team with usage issues.
- Purpose: Long-term recurring revenue & client trust.
Your feedback will be highly appreciated
0
4 comments
Pilot customer Pay vs Free
skool.com/software-engineering
A community to help you become the best software engineer
Leaderboard (30-day)
1
+9
2
+6
3
+3
4
+3
5
+2
Powered by