SERVICE BUSINESS PLATFORM
Founder & Project Lead · BlooGoo
Multi-tenant platform that connected customer acquisition all the way through scheduling, fulfillment, payment, and reviews for service businesses.
THE CHALLENGE :
THE CHALLENGE :
THE CHALLENGE :
The client could see where website traffic came from, but lost all visibility once someone became a customer. They had no reliable way to connect marketing source to actual appointments, completed work, revenue, or repeat business. As the owner of the firm, I worked directly with the client to redefine the problem from “better analytics” into a full operational platform that preserved attribution across the entire customer lifecycle, and that could eventually serve other service businesses.
APPROACH & KEY DECISIONS :
APPROACH & KEY DECISIONS :
APPROACH & KEY DECISIONS :
I focused on creating a permanent link between acquisition source and long-term customer value, then used that foundation to build a broader multi-tenant product.
Key decisions included:
Capturing source data early and attaching it permanently to the customer record
Designing for multi-tenancy so the system could support many businesses
Making scheduling, communications, and routing highly configurable by each operator
Using Google Maps API to optimize appointment grouping and technician routing
Building automated review collection and revenue-by-source reporting
Growing and directing the engineering team across multiple iterations of the platform while remaining accountable for both client outcomes and technical direction
SOLUTION & IMPLEMENTATION :
SOLUTION & IMPLEMENTATION :
SOLUTION & IMPLEMENTATION :
I owned the client relationship, product vision, and overall delivery while leading the engineering effort as the platform evolved. Early on I worked with a small team; later I directed separate frontend and backend groups as the system grew in scope.
The platform included:
Source-capturing landing experiences
Permanent attribution on customer records
Configurable multi-step scheduling
Automated email and SMS communications
Geographic schedule optimization and technician routing
Automated review request flows
Administrative tools and reporting focused on revenue by channel
Multi-tenant architecture, public sites, APIs, and payment integration
I stayed closely involved in architectural decisions and client priorities while building the team’s ability to execute independently.
RESULTS & IMPACT :
RESULTS & IMPACT :
RESULTS & IMPACT :
Increased operator capacity by nearly one full job per day through more effective routing and scheduling
Reduced average ad spend by ~35% by making it easy to identify underperforming channels
Improved average customer retention by 47% through better communication and customer experience
Gave operators clear visibility into which marketing channels produced actual revenue
Turned a custom solution into a reusable multi-tenant platform
Demonstrated the value of designing attribution and operations as one connected system
WHAT I LEARNED :
WHAT I LEARNED :
WHAT I LEARNED :
Owning both the client conversation and the technical direction made it possible to keep expanding the ambition of the system instead of stopping at a narrower analytics solution. The most durable products come from staying close to the real operational pain while simultaneously building a team that can carry increasing amounts of the execution load.
TECHNOLOGIES :
TECHNOLOGIES :
TECHNOLOGIES :
C# · ASP.NET · SQL Server · Google Maps API · Twilio · Stripe · Multi-tenant architecture · AWS
SERVICE BUSINESS PLATFORM
Founder & Project Lead · BlooGoo
Multi-tenant platform that connected customer acquisition all the way through scheduling, fulfillment, payment, and reviews for service businesses.
THE CHALLENGE :
THE CHALLENGE :
THE CHALLENGE :
The client could see where website traffic came from, but lost all visibility once someone became a customer. They had no reliable way to connect marketing source to actual appointments, completed work, revenue, or repeat business. As the owner of the firm, I worked directly with the client to redefine the problem from “better analytics” into a full operational platform that preserved attribution across the entire customer lifecycle, and that could eventually serve other service businesses.
APPROACH & KEY DECISIONS :
APPROACH & KEY DECISIONS :
APPROACH & KEY DECISIONS :
I focused on creating a permanent link between acquisition source and long-term customer value, then used that foundation to build a broader multi-tenant product.
Key decisions included:
Capturing source data early and attaching it permanently to the customer record
Designing for multi-tenancy so the system could support many businesses
Making scheduling, communications, and routing highly configurable by each operator
Using Google Maps API to optimize appointment grouping and technician routing
Building automated review collection and revenue-by-source reporting
Growing and directing the engineering team across multiple iterations of the platform while remaining accountable for both client outcomes and technical direction
SOLUTION & IMPLEMENTATION :
SOLUTION & IMPLEMENTATION :
SOLUTION & IMPLEMENTATION :
I owned the client relationship, product vision, and overall delivery while leading the engineering effort as the platform evolved. Early on I worked with a small team; later I directed separate frontend and backend groups as the system grew in scope.
The platform included:
Source-capturing landing experiences
Permanent attribution on customer records
Configurable multi-step scheduling
Automated email and SMS communications
Geographic schedule optimization and technician routing
Automated review request flows
Administrative tools and reporting focused on revenue by channel
Multi-tenant architecture, public sites, APIs, and payment integration
I stayed closely involved in architectural decisions and client priorities while building the team’s ability to execute independently.
RESULTS & IMPACT :
RESULTS & IMPACT :
RESULTS & IMPACT :
Increased operator capacity by nearly one full job per day through more effective routing and scheduling
Reduced average ad spend by ~35% by making it easy to identify underperforming channels
Improved average customer retention by 47% through better communication and customer experience
Gave operators clear visibility into which marketing channels produced actual revenue
Turned a custom solution into a reusable multi-tenant platform
Demonstrated the value of designing attribution and operations as one connected system
WHAT I LEARNED :
WHAT I LEARNED :
WHAT I LEARNED :
Owning both the client conversation and the technical direction made it possible to keep expanding the ambition of the system instead of stopping at a narrower analytics solution. The most durable products come from staying close to the real operational pain while simultaneously building a team that can carry increasing amounts of the execution load.
TECHNOLOGIES :
TECHNOLOGIES :
TECHNOLOGIES :
C# · ASP.NET · SQL Server · Google Maps API · Twilio · Stripe · Multi-tenant architecture · AWS
SERVICE BUSINESS PLATFORM
Founder & Project Lead · BlooGoo
Multi-tenant platform that connected customer acquisition all the way through scheduling, fulfillment, payment, and reviews for service businesses.
THE CHALLENGE :
THE CHALLENGE :
THE CHALLENGE :
The client could see where website traffic came from, but lost all visibility once someone became a customer. They had no reliable way to connect marketing source to actual appointments, completed work, revenue, or repeat business. As the owner of the firm, I worked directly with the client to redefine the problem from “better analytics” into a full operational platform that preserved attribution across the entire customer lifecycle, and that could eventually serve other service businesses.
APPROACH & KEY DECISIONS :
APPROACH & KEY DECISIONS :
APPROACH & KEY DECISIONS :
I focused on creating a permanent link between acquisition source and long-term customer value, then used that foundation to build a broader multi-tenant product.
Key decisions included:
Capturing source data early and attaching it permanently to the customer record
Designing for multi-tenancy so the system could support many businesses
Making scheduling, communications, and routing highly configurable by each operator
Using Google Maps API to optimize appointment grouping and technician routing
Building automated review collection and revenue-by-source reporting
Growing and directing the engineering team across multiple iterations of the platform while remaining accountable for both client outcomes and technical direction
SOLUTION & IMPLEMENTATION :
SOLUTION & IMPLEMENTATION :
SOLUTION & IMPLEMENTATION :
I owned the client relationship, product vision, and overall delivery while leading the engineering effort as the platform evolved. Early on I worked with a small team; later I directed separate frontend and backend groups as the system grew in scope.
The platform included:
Source-capturing landing experiences
Permanent attribution on customer records
Configurable multi-step scheduling
Automated email and SMS communications
Geographic schedule optimization and technician routing
Automated review request flows
Administrative tools and reporting focused on revenue by channel
Multi-tenant architecture, public sites, APIs, and payment integration
I stayed closely involved in architectural decisions and client priorities while building the team’s ability to execute independently.
RESULTS & IMPACT :
RESULTS & IMPACT :
RESULTS & IMPACT :
Increased operator capacity by nearly one full job per day through more effective routing and scheduling
Reduced average ad spend by ~35% by making it easy to identify underperforming channels
Improved average customer retention by 47% through better communication and customer experience
Gave operators clear visibility into which marketing channels produced actual revenue
Turned a custom solution into a reusable multi-tenant platform
Demonstrated the value of designing attribution and operations as one connected system
WHAT I LEARNED :
WHAT I LEARNED :
WHAT I LEARNED :
Owning both the client conversation and the technical direction made it possible to keep expanding the ambition of the system instead of stopping at a narrower analytics solution. The most durable products come from staying close to the real operational pain while simultaneously building a team that can carry increasing amounts of the execution load.
TECHNOLOGIES :
TECHNOLOGIES :
TECHNOLOGIES :
C# · ASP.NET · SQL Server · Google Maps API · Twilio · Stripe · Multi-tenant architecture · AWS