Find the repeated customer job
Look across actual engagements for a problem that recurs with similar inputs, decisions and outputs. Separate the repeated workflow from the bespoke expertise clients value. A software product may automate the former while the latter remains a service.
Document what users try to do without your team and where they fail. A founder story can suggest a hypothesis, but it does not prove that another agency should build the same product. Do not invent customer interviews or validation results.
Test a narrow product boundary
Choose one complete job: prepare an approved publishing packet, verify delivery or reconcile reports. Define the user, input, result and exception path. A product that solves one job reliably can be evaluated more clearly than a dashboard that partially replaces an entire agency.
Keep the service running responsibly while testing. Preserve client ownership, contracts and data obligations. A new product does not silently expand permission to reuse client information or distribute it to new providers.
Price the ongoing obligation
Software retains hosting, support, onboarding, maintenance and incident work. Subscription revenue is not gross profit. Estimate variable cost per customer and fixed monthly operating cost, then compare the contribution with the investment required to build and maintain the product.
The worksheet calculates a simple steady-state scenario. It excludes churn dynamics, acquisition cost, taxes and financing unless you model them elsewhere. A positive monthly contribution does not prove demand or retention.
Use paid behavior and retention as evidence
Track whether users complete the core job, return when the need recurs and continue paying. Record support effort and cancellations. A service customer accepting a discounted pilot is useful evidence, but it may not represent a self-serve buyer.
When agents connect to customer accounts, preserve explicit authorization boundaries. The MCP security guidance is relevant to tool-mediated access; convenience does not remove consent and credential responsibilities.
Choose the next investment deliberately
Expand the product only when the observed job, willingness to pay and support burden support it. A hybrid business can remain a sensible outcome. The goal is a repeatable useful service, not adopting a SaaS label before the economics and customer behavior exist.