B2B SaaS positioning + conversion copy
Independent product conceptI began with a familiar agency-SaaS idea: spot margin drift earlier. Competitor research showed that position was already occupied. So the real work became killing the attractive first answer—and finding a narrower commercial decision worth building around.
01 / The assignment
The exercise was deliberately larger than “write a SaaS landing page.” The goal was to show the decisions that should precede copy: who owns the problem, what happens in the current workflow, what the market already promises, which claims are supportable and what the page must make a sophisticated buyer believe next.
Because ScopeSignal is fictional, the truth constraint mattered as much as persuasion. The finished work could demonstrate a problem, a mechanism and a user experience. It could not honestly claim availability, automation, integration coverage, customer outcomes or price.
02 / The attractive first answer
The initial position described an “early-warning layer” between project activity and agency margin. A named Margin Drift Timeline would connect approved scope, unplanned work and delivery cost before the retrospective.
Original mechanism
Small changes stay scattered across tools, so the agency cannot see their combined financial effect early enough.
Combine the signals.
Move the insight earlier.
Name the new visual.
Complete the SaaS page.
03 / Three research rounds
The discovery questions created the map. Public sources could answer market, workflow, competitor and hiring questions. Product feasibility, willingness to pay and outcomes remained intentionally unresolved.
Agency research supported a real commercial pressure: small firms dominate the market, mixed pricing models are common, and scope creep is repeatedly discussed as absorbed work and delayed change control.
This round broke the old position. Productive, Scoro and Teamwork already describe live or forecast margin visibility. Docket, ScopeGuard and similar tools already frame requests, impact and approvals.
The research shifted from category invention to the decision the workflow should force. Upwork briefs also showed that buyers want positioning, value proposition, objections and complete homepage thinking—not copy decoration.
Research ceiling: internet sources cannot validate demand, price, feasibility, accuracy, security, adoption or outcomes. Those require customer discovery, product work and market testing.
04 / The contradiction
Publicly markets real-time profitability, future profit forecasting and budget warnings. The “early visibility” territory is occupied.
Public documentation describes forecasted cost, income, margin and project “watchdogs.” Margin monitoring is not missing from the category.
Markets budget health, live margins and action before a post-mortem. The retrospective contrast is directly claimed.
Docket, ScopeGuard, Fenscope, Ersilia, Vinrova and ScopePilot already cover combinations of scope comparison, impact, change orders and approval. Detection plus documentation is also crowded.
05 / The strategic pivot
The strongest surviving insight was less dramatic and more useful: not every extra request should be billed, but every material request needs an explicit commercial response before delivery continues.
Problem mechanism
A deviation enters as normal work. The team begins. No authorised person explicitly chooses to absorb, trade, re-scope or charge. Several defaults accumulate until the margin changes without a conscious decision.
Solution object / Scope Decision Trail
What fee, scope and delivery cost were agreed?
What materially changed, in plain language?
What is the estimated delivery cost and cumulative exposure?
Absorb, trade, re-scope or charge?
Who chose, why, and what needs to be explained to the client?
The product hypothesis changed from “show the margin problem” to “make the commercial choice impossible to leave implicit.”
06 / Buyer and awareness
The page assumes a sophisticated reader who already knows about scope creep, time tracking, PSA software and change orders. It therefore demonstrates the decision model instead of over-explaining the category.
Feels the margin and client-relationship trade-off. Needs to know whether the workflow protects control without forcing an adversarial conversation every time.
Primary question: is this worth changing how we work?Needs reliable rules, ownership and records. Evaluates where the concept fits beside existing project and finance systems.
Primary question: can this become a usable decision process?Sees requests arrive and must preserve momentum. Needs a lightweight path from “client asked” to “someone authorised the response.”
Primary question: will this add clarity or administration?Working ICP, not validated segment: 10–49-person digital, design or development agencies using fixed-fee or capped projects. It is precise enough to guide the page and still honest about the evidence gap.
07 / Message architecture
The page is built for a problem-aware, sophisticated buyer. Its job is not to manufacture scarcity. Its job is to make the decision logic concrete enough to evaluate.
The project can look operationally healthy while the commercial assumption changes underneath it.
Use familiar delivery language so the reader recognises how the problem enters.
Decisionless Delivery explains why “small” exceptions become an uncontrolled pattern.
The Scope Decision Trail turns the concept into five understandable objects.
Project Atlas reveals the arithmetic and four responses through a working interaction.
Fit, non-fit, unknowns and claim boundaries do more persuasive work than a fictional offer.
08 / The finished artifact
The product page contains a complete problem-to-decision argument and an interactive fixed-fee project. Choose how to handle three requests and watch unresolved exposure, added fee, contribution and gross margin update from disclosed assumptions.
09 / Proof discipline
A polished fictional offer would make the page look more complete and the case study less credible. The final version separates executable craft from facts only a real product and real customers could supply.
Allowed on the page
Removed from the page
10 / Selected public sources
Primary product pages and documentation were used for competitor capability checks. Market studies and qualitative discussions were used directionally and kept separate from product proof.
For founders and marketing leads
If your page needs a sharper position, a defensible mechanism and copy that knows which claims it has earned, this case study is the kind of work I bring to the assignment.