01 / Built around your business
Where the opportunity sits
Software buyers need to understand technical fit, delivery responsibility and how a project begins. The starting point is to identify where that decision becomes difficult, then agree which part of the journey deserves attention first.
02 / Built around your business
What the work can include
Service and capability pages, accurately attributed project stories, discovery qualification and proposal follow-up. The scope is agreed around your current systems, operating capacity and priorities. Each deliverable should have an owner, the information needed to complete it and a clear review point.
01 / Fit
Explain who the product helps and why.
Start with the workflow and audience, then show what a useful evaluation involves. Make requirements and limitations visible before a visitor books time or starts an account.
- Separate service and technology pages around capabilities you can demonstrate.
- Use real product information.
- Explain setup and integration dependencies.
- Separate demo requests from suitable opportunities.
The working decision
Explain who the product helps and why.
Use real product information.
02 / First value
Define the milestone beyond account creation.
Agree the action that signals an initial useful outcome. Inspect the steps, questions and dependencies between entry and that milestone with the team that owns the product.
- Show genuine project scope, working methods and technical decision-making.
- Confirm the event and eligible population.
- Make help available at the point of friction.
- Assign ownership of product changes.
The working decision
Define the milestone beyond account creation.
Confirm the event and eligible population.
03 / Continued use
Look for a continuing reason to use the product.
Review usage and customer feedback by a consistent cohort. Coordinate useful education, support and commercial communication without treating every reminder as a retention improvement.
- Keep scoping, proposals and technical questions connected in the pipeline.
- Keep usage and paid continuation distinct.
- Match messages to the customer’s situation.
- Review the period and limitations of the cohort.
The working decision
Look for a continuing reason to use the product.
Keep usage and paid continuation distinct.
03 / Built around your business
Build around how your customers choose
1. Find relevant expertise
Separate service and technology pages around capabilities you can demonstrate.
2. Assess the delivery team
Show genuine project scope, working methods and technical decision-making.
3. Discuss a requirement
Capture business context and project stage before asking for sensitive specifications.
4. Support procurement
Keep scoping, proposals and technical questions connected in the pipeline.
04 / Built around your business
Measure the decisions that matter
Qualified project enquiries, discovery calls and proposal progression. Start with a reliable baseline and keep early interactions separate from completed outcomes. Review the results against your capacity and the costs included in the plan, so the next decision is based on useful business information.
How is software-house marketing different from SaaS marketing?
A software house sells delivery capability and a scoped engagement. Its pages should explain responsibilities, project fit and the discovery process; SaaS pages focus on a repeatable product and activation.
Send everyone to a demo?
Choose the route that fits the product and buying process. A complex evaluation may need a person; a straightforward use case may benefit from a direct trial.
Judge growth by registrations alone?
Track whether suitable users reach value and continue. Keep sign-ups, activation, paid conversion and expansion visible as separate stages.
Qualified interest
Demo, consultation or trial requests meeting the agreed audience and use-case criteria.
Enquiry context, qualification and evaluation records.
Initial value
Eligible users or accounts reaching the agreed first useful milestone.
Product or delivery events checked against the milestone definition.
Paid progression
Qualified evaluations becoming paid relationships within the stated window.
CRM and billing records, reported separately from trial starts.
Continued value
The defined starting cohort continuing useful activity or a paid relationship.
Usage, customer feedback and billing records for the cohort.
05 / Built around your business
How the engagement starts
Share your website, target market and the main point where growth is getting stuck. We review the existing journey and the information your team can provide, then recommend a defined starting scope. The proposal separates agency work, advertising spend and third-party costs. It also identifies your team’s responsibilities, access requirements and review points.
A useful page or journey
Delivery engagement models, project role captions and discovery checklist.
Information your team supplies
Current service or product facts, coverage and availability, plus the details needed to support “Assess the delivery team”.
Implementation & ownership
Agree who makes the changes and who handles the next step when a customer is ready to “discuss a requirement”.
A defined review
Review qualified project enquiries, discovery calls and proposal progression. Record the period, source and the next action the findings support.
Before we start
Questions about the work
How is software-house marketing different from SaaS marketing?
A software house sells delivery capability and a scoped engagement. Its pages should explain responsibilities, project fit and the discovery process; SaaS pages focus on a repeatable product and activation.
What determines cost and timing?
The target market, the amount of work, access to the right systems and the review process all affect the scope. We explain the deliverables and dependencies in the proposal.
