[ DRAFT_ / SYSTEM LIBRARY ]

See some of the systems we build.

Every business works differently. These are examples of systems DRAFT can design around common operational problems.

NOTE — THESE ARE ILLUSTRATIVE EXAMPLES. THEY DESCRIBE TYPICAL SCENARIOS, NOT SPECIFIC EXISTING CLIENTS OR ENGAGEMENTS.

[01] THE LIBRARY

[ THE SCENARIO ]

A regional building contractor receiving enquiries through their website, phone, email and referrals — all landing in different places.

[ THE PROBLEM ]

Enquiries arrive through multiple channels and sit in inboxes until someone has time to look at them. Good jobs are responded to late, poor-fit jobs consume estimator time, and nothing is tracked consistently.

[ THE SYSTEM ]

DRAFT could build a single intake layer that captures every enquiry regardless of source, qualifies it against the contractor's criteria — location, job type, budget, timeframe — and routes it into one pipeline with the right person alerted.

[ THE WORKFLOW ]

  1. ENQUIRY
  2. CAPTURE
  3. QUALIFY
  4. CRM
  5. TEAM ALERT
  6. FOLLOW-UP

[ THE OUTCOME ]

  • FASTER RESPONSE TO EVERY ENQUIRY
  • CONSISTENT LEAD QUALIFICATION
  • ESTIMATOR TIME SPENT ON REAL OPPORTUNITIES

[ THE SCENARIO ]

An independent car dealership group handling a steady flow of enquiries about vehicles, part-exchanges and servicing across several sites.

[ THE PROBLEM ]

Follow-up depends entirely on individual salespeople remembering. Busy weekends mean enquiries from Friday are cold by Tuesday, and there is no visibility of who has been contacted and who has not.

[ THE SYSTEM ]

DRAFT could build a follow-up system that organises every enquiry into a structured sequence — acknowledging instantly, scheduling the next touch automatically, surfacing overdue follow-ups and giving management a clear view of the pipeline.

[ THE WORKFLOW ]

  1. ENQUIRY
  2. ACKNOWLEDGE
  3. SEQUENCE
  4. REMIND
  5. ESCALATE
  6. REPORT

[ THE OUTCOME ]

  • FEWER OPPORTUNITIES DISAPPEARING
  • LESS MANUAL ADMIN FOR THE SALES TEAM
  • BETTER VISIBILITY OF FOLLOW-UP ACTIVITY

[ THE SCENARIO ]

An accountancy practice receiving a constant stream of client documents — statements, invoices, receipts and signed forms — by email and post.

[ THE PROBLEM ]

Staff spend hours opening attachments, reading documents, extracting figures and rekeying them into practice software. Errors creep in, and anything unusual waits in the same queue as everything else.

[ THE SYSTEM ]

DRAFT could build a document pipeline that receives incoming files, extracts the important information, validates it against expected formats and client records, updates the relevant systems — and flags only the exceptions for a person to review.

[ THE WORKFLOW ]

  1. RECEIVE
  2. EXTRACT
  3. VALIDATE
  4. UPDATE
  5. FLAG
  6. REVIEW

[ THE OUTCOME ]

  • FAR LESS MANUAL DATA ENTRY
  • EXCEPTIONS SURFACED INSTEAD OF BURIED
  • A CONSISTENT, AUDITABLE PROCESS

[ THE SCENARIO ]

A growing online retailer handling hundreds of customer messages a week across email, chat and social channels.

[ THE PROBLEM ]

The same questions — where is my order, how do I return this, can I change my address — take up most of the support team's day, while genuinely complex issues wait behind them in the same queue.

[ THE SYSTEM ]

DRAFT could build a support layer that classifies every incoming request, resolves common queries automatically using order and policy data, retrieves order information on demand, and escalates complex issues to the right person with full context attached.

[ THE WORKFLOW ]

  1. REQUEST
  2. CLASSIFY
  3. RESOLVE
  4. RETRIEVE
  5. ESCALATE
  6. LOG

[ THE OUTCOME ]

  • FASTER ANSWERS FOR CUSTOMERS
  • SUPPORT TIME FOCUSED ON REAL PROBLEMS
  • EVERY CONVERSATION LOGGED AND SEARCHABLE

[ THE SCENARIO ]

A consultancy firm whose partners rely on monthly performance reporting pulled from practice management, finance and project tools.

[ THE PROBLEM ]

Producing each month's report means someone manually exporting from several systems, cleaning the data in spreadsheets and rebuilding the same deck. It takes days, and the numbers are already out of date when presented.

[ THE SYSTEM ]

DRAFT could build a reporting system that consolidates information from each source automatically, applies the firm's definitions consistently, and prepares recurring reports on schedule — with the underlying data always available to interrogate.

[ THE WORKFLOW ]

  1. SOURCES
  2. CONSOLIDATE
  3. CLEAN
  4. CALCULATE
  5. REPORT
  6. DISTRIBUTE

[ THE OUTCOME ]

  • RECURRING REPORTS PREPARED AUTOMATICALLY
  • ONE CONSISTENT VERSION OF THE NUMBERS
  • DAYS OF MANUAL WORK REMOVED EACH MONTH

[ THE SCENARIO ]

A property management company coordinating maintenance requests from tenants across a large portfolio of buildings.

[ THE PROBLEM ]

Requests arrive by phone, email and portal, and coordinating them means chasing contractors, checking information and updating tenants by hand. Things slip, and nobody has a complete picture of what is outstanding.

[ THE SYSTEM ]

DRAFT could build an operations system that collects every request in one place, gathers any missing information automatically, assigns tasks to the right contractor or team member, and keeps tenants and managers updated at each step.

[ THE WORKFLOW ]

  1. REQUEST
  2. COLLECT
  3. TRIAGE
  4. ASSIGN
  5. NOTIFY
  6. TRACK

[ THE OUTCOME ]

  • FEWER REPETITIVE COORDINATION TASKS
  • CLEAR VISIBILITY OF OUTSTANDING WORK
  • TENANTS KEPT INFORMED WITHOUT CHASING

[ THE SCENARIO ]

A B2B services firm with a small sales team managing a long, relationship-driven sales cycle across many live opportunities.

[ THE PROBLEM ]

Lead information lives in inboxes, follow-ups live in diaries, and the CRM is updated only when someone has spare time — which means it is rarely accurate. Proposals go out late and pipeline reviews are guesswork.

[ THE SYSTEM ]

DRAFT could build a connected sales workflow where lead information is captured once, follow-ups are scheduled automatically, the CRM updates itself as things happen, and the right people are notified at each stage — from first contact to proposal.

[ THE WORKFLOW ]

  1. LEAD
  2. CAPTURE
  3. NURTURE
  4. CRM UPDATE
  5. PROPOSAL
  6. NOTIFY

[ THE OUTCOME ]

  • A CRM THAT REFLECTS REALITY
  • CONSISTENT FOLLOW-UP ON EVERY OPPORTUNITY
  • BETTER VISIBILITY OF THE REAL PIPELINE

[ THE SCENARIO ]

A business whose most important process doesn't fit any off-the-shelf category — a particular way of quoting, scheduling, approving or delivering that has evolved over years.

[ THE PROBLEM ]

Generic software forces the business to work around it. The team maintains spreadsheets and workarounds to bridge the gap between how the software works and how the business actually operates.

[ THE SYSTEM ]

DRAFT designs systems around unique business processes rather than forcing businesses into predetermined templates. We map how work really flows, then build exactly what is needed — nothing more, nothing generic.

[ THE WORKFLOW ]

  1. MAP
  2. DESIGN
  3. BUILD
  4. INTEGRATE
  5. REFINE
  6. SUPPORT

[ THE OUTCOME ]

  • SOFTWARE THAT MATCHES HOW YOU WORK
  • WORKAROUNDS AND SPREADSHEETS RETIRED
  • A SYSTEM THAT CAN EVOLVE WITH THE BUSINESS

[ NEXT STEP ]

Not sure which system fits your business?

Answer six questions and we'll point you at the system most likely to make a difference.