Intown x Jemini
How Intown Plumbing Turned a $50K Software Idea Into a Validated SaaS Product in 60 Days
Using Jemini's Value Engineering Process to identify the 2 features that mattered most—and avoid building the other 18.
Project Snapshot
🧑🔧Client: Intown Plumbing | Whodo
🎯 Project Goal: Validate a new SaaS product before making a larger software investment
⏱️ Timeline: 60 Days
👥 Team: Fractional CTO, UX Designer, Full-Stack Developer
💰 Investment: $50,000
📈 Results: +32% Consultations, $4,200 Saved, 12 Hours Saved Weekly
🧠 Methodology: Value Engineering Process + Build Blueprint
The Problem: Too Many Ideas, Not Enough Clarity
When Intown Plumbing came to Jemini, they had a strong vision for a customer-facing application that would integrate with ServiceTitan and improve the customer experience.
The challenge wasn't whether the idea had potential. The challenge was determining what should actually be built.
Like many business owners, they had:
A long list of product ideas
A limited budget
A desire to move quickly
Uncertainty about where to start
They had also attempted to move the project forward previously, but the effort stalled before the application could be completed.
They didn't want another drawn-out software project.
They wanted clarity.
They wanted momentum.
And most importantly, they wanted proof that the product could create value before making a larger investment.
Most founders don't fail because they lack vision. They fail because they invest in the wrong features first.
The Results: Business Validation Before Bigger Spending
Outcomes
📈 32% increase in consultations booked
💰 $4,200 saved by reducing unnecessary truck rolls
⏱️ 12 hours saved per week through virtual lead qualification
✅ Working MVP that validated the concept
🚀 Clear roadmap for future product development
Rather than building every feature on the wish list, we focused on validating the concept first.
Within 60 days, Intown Plumbing launched a working SaaS MVP that produced measurable business outcomes.
Why This Matters
For most founders, the biggest risk isn't building software.
It's spending $100,000+ on software before knowing whether it will create business value.
This project provided evidence before expansion.
Instead of making a large investment based on assumptions, Intown Plumbing gained confidence through real-world results.
We came to Jemini with a vision for a customer-facing application but weren't sure what the first version should look like. They helped us break down the idea, prioritize the features that mattered most, and create a clear roadmap for moving forward.
Rather than trying to build everything at once, they focused on solving the most important problems first. Their team handled the product planning, design, development, and launch process, making it easy for us to stay focused on running our business.
The MVP was delivered in about two months and helped us increase consultations, reduce unnecessary truck rolls, and save time qualifying leads. Just as importantly, it gave us confidence that the concept worked and provided a clear path for future development.
Dan and the team at Jemini are unique in the fact that they aren't just dev wizards cranking out code, but also very personable and cared about connecting and understanding us in order to develop a tool/system that really resonates with us and our needs. They weren't just building something for us, but WITH us.
If you're a business owner looking to build software and want a team that understands both technology and business outcomes, I'd recommend talking with Jemini.
★★★★★
What We Didn't Build
This is where most SaaS MVP development projects go off track.
The original vision contained more than twenty possible features.
Through Jemini's Value Engineering Process, we determined that only two capabilities were required to validate the concept.
What We Built
Video consultations between homeowners and technicians
ServiceTitan scheduling integration
What We Deliberately Did Not Build
Mobile applications
Customer portals
Billing systems
Reporting dashboards
Admin analytics
Notification systems
Advanced workflow automation
Not because those features weren't valuable.
Because they weren't necessary yet.
Most software firms sell features.
We eliminate them.
The result is faster validation, lower risk, and better use of capital.
How Jemini Approached the Project Differently
1. Value Engineering Process
Before writing a single line of code, we mapped business outcomes directly to implementation work.
This allowed us to identify which features would create immediate value and which could wait.
Instead of building everything, we built the right things.
2. Build Blueprint
Using our Build Blueprint methodology, we translated the founder's vision into a clear execution plan.
Every user action, system event, and business objective was mapped before development began.
This reduced ambiguity, improved delivery speed, and aligned everyone around the same outcome.
3. Fractional Product Team
Rather than requiring the founder to hire and manage multiple specialists, Jemini assembled the exact team required for the project.
Fractional CTO
UX Designer
Full-Stack Developer
The owner remained involved in key product decisions but never had to manage developers, delivery schedules, or technical execution.
We owned the process.
They focused on running the business.
4. Rapid MVP Execution
Using modern AI-assisted development workflows and disciplined project management, we delivered the MVP in just 60 days.
Fast enough to create momentum.
Structured enough to maintain quality.
Many founders come to us after realizing they don't need cheaper developers.
They need someone who can determine what should be built, assemble the right team, and protect the budget.
That's where our process differs.
Why Founders Choose Jemini
Founders don't hire us because we write code.
They hire us because we help them make better product decisions.
What Makes Jemini Different
Proven SaaS MVP Development process
Fractional CTO leadership
Value Engineering methodology
Build Blueprint planning framework
Event Storming workshops
Domain Driven Design expertise
Experience leading offshore and fractional teams
Background in SaaS, AI, IoT, and enterprise systems
Our goal isn't to build more software.
Our goal is to help founders build the right software.
A Simple 3-Step Plan to Build Your SaaS Product
Step 1: Create Your Build Blueprint
Identify the smallest product capable of generating measurable business value.
Step 2: Launch Your MVP
Build only what is necessary to validate the concept and gather market feedback.
Step 3: Scale With Confidence
Use real-world data to determine where future development dollars should be invested.