Define the first complete journey
Specify what a user can create, review, update and export. Agree acceptance criteria for each step before adding secondary features.
Define the smallest useful product, agree its acceptance criteria and build around the people who will actually use it.
Prices cover the listed scope. Additional work and external costs are quoted separately.
An effective first release covers the important user journey and the controls that keep it dependable.
Specify what a user can create, review, update and export. Agree acceptance criteria for each step before adding secondary features.
Document account roles, organisation boundaries and sensitive actions. Check permissions on the server as part of the implementation scope.
Plan validation, error states, recovery and security checks alongside the feature work. Use an agreed verification checklist to make handover reviewable.
The verification standard is a planning reference; a certification or independent security audit is a separate engagement.
Platform reference: OWASP: Application Security Verification Standard
Define and build one core product workflow with up to two user roles, six key screens and one agreed integration.
Map the user problem, two roles, essential screens and the integration boundary.
Approve an acceptance backlog and explicitly record features reserved for later releases.
Develop the agreed screens and permissions through staged demonstrations.
Each milestone can be reviewed against the specified user tasks and access rules.
Check normal tasks, invalid inputs, role restrictions and integration failures.
Record passed checks, defects and accepted limitations before release.
Hand over source, deployment access and operating instructions.
Assign hosting and support ownership, with the agreed thirty-day defect window documented.
Accepted feature backlog, source repository, deployment instructions and operating notes for the agreed first release.
Outside this scope: Mobile native apps, regulated-system certification, open-ended backlog, infrastructure charges and 24/7 operations
6–10 weeks for the defined scope after discovery
Discovery $750 – $1,500; hosting and maintenance separate
Discovery defines the implementation scope and quote. Proposed milestone billing is 40% at start, 30% at approved build and 30% at acceptance, subject to the agreed contract.
If the full scope is beyond your budget, we’ll prioritise the most useful work and agree a smaller first phase with you.
Share what is available. We’ll identify any missing access or inputs during scoping.
Published prices apply to the listed scope. Deliverables, timing, revisions and external costs are confirmed before work starts.
An illustrative delivery approach to help you review the scope. This is a planning example, not a client case study.
| Stage | Example work | Acceptance or decision |
|---|---|---|
| Discovery | Define a listing submission and review workflow for two user roles. | Agree the screen list, permissions and one integration boundary. |
| Reviewable build | Demonstrate a submission, review decision and published record using test records. | Check rejected/invalid inputs and role restrictions as well as the happy path. |
| Handover | Transfer the agreed source, deployment instructions and operating notes. | Sign off the backlog; assign hosting, support and any remaining work. |

Keep the conversation going when your team is busy. ScaleXTalk handles business calls, collects caller details, qualifies enquiries and supports appointment booking.
ScaleXTalk is the voice product. ScaleXSol can scope the business setup, call rules, integration, testing and management separately. Confirm the selected product plan and deployment requirements in the combined quote.
Listen to the roofing, plumbing and HVAC call recordings on the AI receptionist service page to assess the voice and responses. Before deployment, also test appointment booking, interruptions and human fallback against your business rules.
One-time setup, recurring management, the product/platform plan, telephone numbers and call usage. The management allowance alone is not the total operating cost.

Help customers find service providers by category and location. ScaleXBizz brings business profiles, service information and contact details into one place.
Prepare your business name, category, service location, website and contact information. Use the directory enquiry to discuss a listing and who can keep its information current.
The directory supports discovery by service and location, with profiles and provider contact details. Tell us the service and area you need when asking about access.
Request the current listing options, review criteria and any charges before submitting business information. A listing does not imply a guaranteed enquiry volume or a paid endorsement.
Illustrative platform screens show the type of work and reporting. These are not client results.
Review desktop and mobile layouts together before implementation.
Review application records and workspace access as part of the data model.
Inspect requests, responses and validation checks for a defined integration.
Track acceptance checks, review decisions and the material needed for handover.
Explore eight illustrative projects, from the initial brief to delivery and acceptance. Businesses and data in these walkthroughs are fictional.
A focused client portal with clear access boundaries.
Illustrative project
Explore the walkthroughStart here for a content or service website.
Check whether an integration can solve the task.
The defined MVP allowance covers one validated workflow, up to two roles, six key screens and one integration. Discovery turns the idea into an acceptance backlog and identifies dependencies before an implementation commitment. Review staged demonstrations against that backlog; new features require an explicit scope and price decision.
ScaleXTalk and ScaleXBizz are shown below as owner-supplied products. Use their available overview and public product link to understand the use cases. A project proposal should identify the team’s precise delivery role and provide an appropriate working walkthrough.
The proposed scope includes source/deployment handover and a thirty-day defect correction window. Hosting, ongoing operations, new features and around-the-clock support are separate responsibilities. Agree acceptance, ownership and maintenance before the final milestone.
$8,000 – $20,000 / defined MVP. Discovery $750 – $1,500; hosting and maintenance separate These are published USD prices. The written quote must state the complete cost, payment schedule and applicable taxes.
6–10 weeks for the defined scope after discovery. To scope the work, prepare: User problem; must-have workflow; roles/integrations. The schedule starts after the required access, inputs and approvals are ready.
Use the listed deliverables and exclusions as the starting point. The quote must state acceptance checks, review rounds, payment stages, cancellation arrangements and any ongoing support. Requested additions need an agreed cost and schedule before implementation.
Tell us where you are, what needs to change, and what success would look like for your business.