Custom sales workflow systems

A sales workflow fitted to how your team actually sells.

A custom sales workflow system connects lead capture, ownership, quoting, approvals, follow-up, and reporting around the way your team already works. It makes sense when standard tools leave important handoffs manual, fragmented, or unclear.

qraft starts with one workflow, builds a focused pilot, and improves the working system with the people who use it.

Talk through your workflow See a working demonstration

A standard product may be the better answer. The first step is understanding the workflow—not assuming a custom build.

What is a custom sales workflow system?

One connected flow from enquiry to follow-up.

A sales workflow system defines how a new opportunity enters the business, who owns it, which information must be captured, when a quote is ready, who approves the next step, and how follow-up is recorded.

A custom system adapts those stages to the team’s real roles, terminology, rules, and tools. It does not begin with a generic pipeline and force every team into the same fields. It begins by mapping how work moves today, including the exceptions that spreadsheets and chat messages usually hide.

Custom does not need to mean rebuilding every tool. A fitted workflow may preserve the systems that already work and connect only the handoffs that are fragile.

When does custom work make sense?

Look for broken handoffs—not a longer feature list.

The strongest signal is not that a spreadsheet looks untidy. It is that important work repeatedly loses context, ownership, or momentum when it moves between people or tools.

01Leads enter through several channels.Website forms, exhibitions, referrals, calls, and messages produce different levels of information.
02Ownership becomes unclear.The team cannot quickly see who should act next or whether that action happened.
03Quoting repeats the same reconstruction.Customer context, products, pricing, terms, and approvals are copied between systems for every job.
04Exceptions live in chat.Discounts, unusual requirements, approval decisions, and follow-up promises are hard to trace later.
05Reporting requires manual cleanup.Managers reconcile sheets or ask individuals for the current state of work.
06The standard tool is heavily worked around.The team exports data, maintains parallel sheets, or avoids the system because its stages do not match the real process.

One weak handoff may justify a focused pilot. It does not automatically justify replacing the full sales stack.

What can the system connect?

Connect the work that must move together.

The agreed pilot may include only one or two of these groups. qraft does not claim to replace accounting, invoicing, enterprise CPQ, e-signature, or every CRM function.

Capture and intake

Collect enquiries, referrals, event leads, forms, cards, files, or messages with the context needed for the next decision.

Ownership and qualification

Assign responsibility, record status, preserve conversation context, and make readiness requirements visible.

Client and opportunity management

Keep the people, company, job, source, and next action connected rather than re-entering them at each stage.

Quoting and approvals

Prepare quote-ready information, use controlled pricing or catalog data where appropriate, and keep human confirmation before consequential actions.

Follow-up

Carry the relevant context into reminders, calls, email, WhatsApp, or another agreed channel without making one channel the centre of the system.

Reporting

Show the operational state of leads, ownership, quotes, and follow-up using the fields the team actually maintains.

Standard CRM, connected tools, or custom system?

Choose the smallest approach that fits the real process.

OptionBest whenMain trade-off

Spreadsheet or shared document

Best whenOne person owns a simple process and the volume is manageable

Main trade-offOwnership, history, validation, and reminders depend on manual discipline

Standard CRM

Best whenThe team can adopt common stages and available configuration covers the important rules

Main trade-offThe team may need to change terminology or keep specialist work elsewhere

Connected existing tools

Best whenThe current tools are useful and only a few handoffs need automation

Main trade-offMore connections can create hidden dependencies and exception handling

Custom sales workflow system

Best whenRoles, rules, approvals, data, or handoffs are specific enough that workarounds are becoming the process

Main trade-offRequires clear ownership, testing, and an ongoing improvement relationship

Choose a standard CRM when its model already matches the team closely. Connect existing tools when the problem is a small number of predictable transfers. Consider a fitted system when the operating model itself is specific and the exceptions matter.

What should the first pilot include?

One useful outcome with a clear boundary.

The first pilot should prove one operational improvement without attempting a full migration. It needs a clear starting event, required information, ownership rule, review point, and completed outcome.

Start: a qualified enquiry is captured.

Required context: client, job, source, need, timing, owner, and consent where relevant.

Decision: the lead is ready—or not ready—to progress.

Output: a reviewed quote draft and a recorded next action.

Excluded: accounting migration, invoicing, broad marketing automation, and every historical data source.

Pilot checklist

01Which event starts the workflow?
02Which information is genuinely required?
03Who owns the next decision?
04Which exceptions need human review?
05What observable outcome completes the pilot?
06Which systems remain unchanged?
07What evidence will determine whether to deploy or revise?

How qraft works with the team

Discover, pilot, deploy, improve.

Discover

Map the current steps, people, tools, terminology, approval points, exceptions, and places where context is lost.

Pilot

Build the smallest working slice that can be tested with realistic inputs and clear review boundaries.

Deploy

Deliver the agreed client-specific system separately from the qraft demonstration environment, with the roles and access required for the workflow.

Improve

Review real use, refine the handoffs, and extend the system only where the next change is justified.

The qraft web app is a working demonstration used to show delivery capability. Client teams receive a separately delivered product adapted to their own process.

Example workflow

From first enquiry to the next clear action.

qraft demonstrates this pattern through its ARCHIDEX 2026 lead-to-quote workflow. The event is one working setting for the method—not the permanent category and not a claimed customer result.

See the working demonstration

01Capturea new enquiry arrives with source and customer context.
02Reviewa person confirms the details and fills any important gaps.
03Qualifythe team records ownership, readiness, timing, and next action.
04Prepareapproved customer and pricing context moves into a quote draft.
05Confirma person reviews the quote before it becomes a client-facing link.
06Follow upthe next action stays connected to the lead and quote history.

Where human review belongs

Automate movement; keep judgment visible.

Automation is useful for carrying known information forward, applying agreed rules, creating reminders, and making incomplete work visible. Human review remains important where the system is interpreting unstructured information, applying contact details, deciding qualification, approving exceptions, or publishing client-facing output.

confirm extracted or imported details before saving
require consent before using contact information where applicable
flag missing context instead of silently inventing it
use approved catalog or pricing data rather than made-up values
confirm before a draft or public quote link is created
make failures and cancelled actions visible

Read the security overview

Common mistakes

What weakens a custom workflow project?

01
Starting with every department.
A broad transformation makes ownership and success difficult to define.
02
Automating an undefined decision.
If the team disagrees about readiness or approval, automation only hides the disagreement.
03
Replacing tools that already work.
Change should be justified by the workflow, not by a desire for one system at any cost.
04
Ignoring exceptions.
The unusual job, incomplete lead, special price, or missing approval often determines whether the system is trusted.
05
Removing human confirmation too early.
Consequential actions need clear review until the inputs and rules are reliable.
06
Measuring activity instead of completion.
More notifications or records do not prove the workflow is working better.

Good fit and poor fit

A fitted system is useful only when the fit matters.

Good fit

the workflow crosses people, stages, or tools
repeated handoffs lose important context
the team can identify one bounded first outcome
operators and managers can participate in testing
the current process includes specific rules or exceptions

Poor fit

a standard product already matches the requirements closely
the request is only for a generic website or document template
nobody owns the workflow or can approve its rules
the expectation is fully autonomous decisions without review
the project depends on unsupported compliance, certification, or performance claims

Common questions

Deciding what fits your sales workflow.

What is the difference between a custom sales workflow system and a CRM?

A CRM typically provides a standard model for contacts, deals, stages, and activities. A custom workflow system may include CRM-like records, but it starts from the team’s specific handoffs, rules, approvals, and outputs. If a standard CRM already fits those needs, it is usually the simpler choice.

Do we need to replace our existing CRM or spreadsheets?

Not necessarily. A focused pilot can preserve existing tools and improve only the handoff that is causing trouble. Replacement should be an outcome of the workflow analysis, not the starting assumption.

What should a small team pilot first?

Choose one repeatable workflow with a clear starting event, owner, review point, and completed outcome. Lead capture to quote readiness is one example; the right boundary depends on where the team currently loses context or momentum.

Can the system include AI?

Yes, where it has a bounded role such as extracting information, assisting with a draft, or identifying missing context. AI output should be reviewed, should use controlled business data where required, and should not silently publish consequential work.

Can WhatsApp be part of the workflow?

It can be one optional channel for lookup, commands, or follow-up when that matches the client’s process. The system may instead use email, forms, calls, another messaging channel, or no messaging integration.

What happens after the pilot?

qraft and the client review what worked, what failed, and which boundaries need revision. A successful pilot can move into a separate client deployment and an ongoing improvement cycle; it does not automatically require a broad rollout.

How much does a custom sales workflow system cost?

Scope and pricing depend on the workflow, integrations, roles, data, and pilot boundary. qraft does not publish a generic package price because the first step is understanding the process well enough to define a responsible scope.

A focused first step

Start with one sales workflow.

Show us how the work moves today. We’ll identify a useful first boundary and explore whether a standard tool, a connected workflow, or a focused pilot is the right next step.