Ripple StrategiesRipple
Software walkthrough · Illustrative example

From Inquiry to Completed Job: A Business Software Workflow

A concrete example of what to scope, test and hand over.

This is an illustrative workflow for a fictional BC service business, not a client deployment or a live application. It follows an invented job, DEMO-104, from inquiry through quotation, scheduling and completion to show the records, permissions, integration boundaries and acceptance checks a useful first release needs. No client records, measured savings or business results are presented.

Start a project

At a glance

01

One job, connected records

A fictional customer, inquiry, quote and job share an identifier, so the next person can see the agreed scope without re-entering it.

02

An accountable next action

Office staff review inquiries, a manager approves quotes, and assigned field staff record completion. Permission is checked for each action.

03

A testable handover

Migration reconciliation, delivery failures, restricted access, backups and a support owner belong in the scope before launch.

Illustrative DEMO-104 workflow — fictional records and proposed behavior
Stage and actorInputAction and outputPermission or acceptance check
Inquiry · OfficeFictional customer Demo Service Co.; job description and preferred dateReview required details; create inquiry DEMO-104 with a responsible staff memberMissing contact details block submission; a duplicate submission does not create a second inquiry
Quote · ManagerReviewed scope, line items and assumptionsApprove a versioned quote and request customer acceptanceOffice staff can prepare a draft; only the manager can approve it. A sent version remains attributable
Schedule · OfficeAccepted quote and available teamCreate an assigned job linked to the accepted scopeAn unaccepted quote cannot become a confirmed job; field staff see only their permitted assignments
Complete · Field staffAssigned job, work notes and completion checklistRecord completion; send the job for office reviewA technician cannot change approved prices or mark another team's job complete
Close · OfficeReviewed job and agreed invoice informationPrepare an export or an approved accounting handoffA failed external handoff stays visible and can be retried without duplicating an invoice

What problem is this workflow designed to solve?

In the fictional example, the inquiry, quote and job currently live in separate files. The proposed first release connects those records and shows the responsible person and next action. Its value would need to be tested against that business's actual work; connecting records alone does not demonstrate time saved or new revenue.

The first decision is whether configuration of an existing CRM or job-management product can support the workflow. Custom software becomes an option when a necessary approval, permission or integration cannot be handled sensibly by the existing tool. The example is a scope discussion, not a reason to replace working software.

Which records and people belong in the first release?

The example needs a customer, an inquiry, quote versions, an acceptance record, an assigned job and a completion record. Each transition retains who acted and when. An edited draft is distinct from an accepted quote, and a completed field checklist is distinct from an office-approved closure.

Office staff manage intake and scheduling, managers approve commercial scope, and field staff work on assigned jobs. A customer receives only the agreed customer-facing information. The server must enforce those permissions as well as the screen: hiding a button is insufficient. Exact roles, retention and customer access are agreed for the real business before implementation.

Where do email, accounting and AI stop?

Email delivery and an accounting handoff are proposed external boundaries in this example, not claims of an existing integration. The project must name the actual provider, available API or export, account owner, approved data fields and permission requirements. A successful local save is distinct from confirmed email delivery or a posted accounting record.

If a provider is unavailable, the job retains its state and exposes the failed handoff to an authorized person. Retries must not send duplicate invoices or silently advance the workflow. If AI is used to draft notes or extract document fields, a person reviews them before approval; AI does not grant permission, accept a quote or post a financial transaction.

How would existing records move safely?

Start with a sample export from the current system, a field map and an agreed rule for duplicate customers and incomplete records. Trial-import that sample, reconcile source and destination counts, inspect linked quotes and jobs, and keep rejected rows with a reason. Preserve a usable copy of the source before the final migration.

The cutover plan identifies who stops edits in the old system, who signs off the reconciliation and how the team returns to the old workflow if the import or acceptance checks fail. Migrating every historical field is a separate scope decision; an approved archive may be more useful than importing records the new system will never use.

What must pass before the team uses it?

Walk DEMO-104 through the happy path with each role, then try the failures: missing contact information, an unauthorized quote approval, an unaccepted quote being scheduled, a technician opening someone else's job, a repeated submit and an unavailable integration. Validate permissions at the API boundary and keep a visible recovery path for rejected actions.

Before launch, the real team should reconcile migration samples, confirm a backup can be restored, test the agreed desktop and mobile devices, and sign off the customer-facing documents. Record those acceptance results against the agreed scope. This guide describes checks to run; it does not claim that an application behind this example has passed them.

Who owns the code, accounts and ongoing support?

Ripple's published custom CRM guidance says clients own their code and there are no per-user fees for Ripple's custom CRM build. That does not transfer ownership of a third-party platform or remove hosting, provider, licensing and maintenance costs. The separate project agreement governs the actual engagement.

For a real workflow, name the repository and deployment account owners, handover materials, backup operator, support contact, maintenance scope and any response commitments in that agreement. Agree how fixes differ from new features and who maintains integrations when providers change. This illustrative example creates no support SLA, delivery deadline or fixed-price offer.

Frequently asked questions

Is this a real client system or an interactive demo?

No. DEMO-104 and Demo Service Co. are fictional. This is a written walkthrough of proposed behavior, with no live application, client data, deployed integration or measured business outcome.

Can Ripple show a relevant software workflow?

Tell us which workflow you need to evaluate. We can discuss a walkthrough using an appropriate demonstration; access to any private customer environment or data depends on authorization. The public website projects on our work page can be inspected now.

Should a business build this instead of using an existing CRM?

Only after checking whether an existing product can support the required workflow, permissions and integrations. Compare configuration, migration, licensing and ongoing support with the scope of a custom build before deciding.

Talk through your project.

Book a call