Integrate
Keep the systems that already work. Connect them so data moves automatically and people stop becoming the integration layer.
Best for disconnected stacksAI Creative · Field guide 02
The BusinessSystemsField Guide
A practical guide to the systems businesses can connect, extend, build or automate, and how to tell which approach makes sense.
- 01Integrate
- 02Extend
- 03Build
- 04Automate
00 · The premise
Your business probably already has custom systems
They just may not look like software. A spreadsheet that 30 people depend on every day is a business system. So is the approval process that lives in email, the report one person rebuilds every Friday, or the customer portal your core platform was never designed to provide.
Most companies do not need more software. They need the right operating layer around the work
01 · Decision framework
Building is only one option
The first job is to choose the right intervention. Sometimes the answer is a custom system. Sometimes it is one good integration. Sometimes the smartest decision is to automate what is already there.
Extend
Add the missing workflow, portal, interface or logic around an ERP, CRM or other core platform instead of replacing it.
Best for a strong core with gapsBuild
Create purpose-built software when the workflow matters, the economics justify it, or the way you operate is genuinely different.
Best for valuable unique workflowsAutomate
Remove repetitive coordination, document handling, reporting and decision support without rebuilding the systems underneath.
Best for repetitive knowledge work→
Good system design starts with the business problem, not the technology. The right answer can be one of these four approaches, or a combination of them.
02 · System atlas
32 systems worth evaluating
Browse by function. Each card shows the problem it addresses and the solution paths that commonly make sense.
01
Operations
Run the workOPS 01
Project Operations Platform
Projects, tasks, budgets, people, documents and status live in separate places.
One operational view from sold work through delivery.
OPS 02
Estimating & Quoting
Estimates depend on spreadsheets, tribal knowledge and manual pricing checks.
Faster, more consistent estimates with margin controls.
OPS 03
Procurement Workflow
Requests, approvals, vendor quotes and purchase orders move through email.
Clear approvals, fewer delays and better spend visibility.
OPS 04
Scheduling & Dispatch
Teams, jobs, equipment and priorities are coordinated manually.
Better utilization with fewer scheduling conflicts.
OPS 05
Inventory & Materials
Stock levels, locations and usage are difficult to trust across sites or teams.
Know what is available, where it is and when to replenish.
OPS 06
Work Orders & Field Service
Jobs move between office staff and field teams with weak status visibility.
A cleaner handoff from request to assignment to completion.
OPS 07
Vendor Management
Supplier information, pricing, documents and performance are scattered.
One source for vendor data, status and commercial history.
OPS 08
Quality & Compliance
Checks, forms, evidence and corrective actions are inconsistent or hard to audit.
Repeatable workflows with a clear record of what happened.
02
Sales & Revenue
Win and expand businessREV 01
CRM Workflow Layer
The CRM stores records but does not match how the sales team actually works.
A sales process people can follow without fighting the CRM.
REV 02
Proposal & Contracting
Quotes, proposals, approvals and contracts are rebuilt manually for every deal.
Faster document generation with cleaner controls and handoffs.
REV 03
Partner / Dealer Portal
Partners need pricing, inventory, documents or status but rely on staff to get it.
Self-service access without exposing the core system.
REV 04
Revenue Operations Dashboard
Pipeline, bookings, delivery and revenue data disagree across systems.
One view of what is likely to close, deliver and bill.
REV 05
Customer Onboarding
Once a deal closes, documents, setup and internal handoffs become manual.
A predictable transition from signed deal to active customer.
03
Finance & Administration
Control money and paperworkFIN 01
Invoice Processing
Invoices arrive in different formats and need manual coding, matching and entry.
Extract, route and validate invoices before they reach accounting.
FIN 02
Approval Workflows
Purchase, expense and exception approvals have no consistent path or audit trail.
Faster decisions with clear authority and history.
FIN 03
Project Profitability
Revenue and cost data arrive too late to see which work is actually making money.
Margin visibility while the project can still be managed.
FIN 04
Contract & Document Control
Commercial documents are hard to find, compare and track through renewal or expiry.
Structured documents, obligations and alerts in one place.
FIN 05
Reconciliation Workbench
Teams spend hours comparing exports from systems that should agree.
Automated matching with people focused only on exceptions.
04
Workforce
Coordinate people and capacityWRK 01
Resource Planning
Leaders know the work coming in but cannot see real capacity by skill, team or date.
Match demand to available people before bottlenecks appear.
WRK 02
Skills & Certification
Credentials, licences and qualifications live in spreadsheets or HR files.
Know who is qualified for what and when credentials expire.
WRK 03
Employee Portal
Policies, forms, requests and internal information are spread across tools.
One useful front door for common employee tasks.
WRK 04
Time & Activity Capture
Time data is late, inconsistent or disconnected from projects and payroll.
Cleaner time data with less chasing and re-entry.
05
Customer Experience
Make the business easier to useCXM 01
Customer Portal
Customers depend on staff for status, documents, requests and routine updates.
Self-service access to the information customers need most.
CXM 02
Booking & Scheduling
Availability, resources, payments and customer details are coordinated across tools.
A booking flow that matches the actual operating rules.
CXM 03
Service Request Portal
Requests arrive through email, phone and forms with inconsistent routing.
One intake path with status, ownership and service history.
CXM 04
Marketplace / Exchange
The business needs to coordinate buyers, sellers, inventory, bids or availability.
A purpose-built transaction layer around a specific market.
CXM 05
Digital Forms & Waivers
Forms are filled, emailed, stored and re-entered manually.
Structured data captured once and routed automatically.
06
Data, Reporting & AI
Turn information into actionDAT 01
Executive Dashboard
Leadership receives lagging reports assembled manually from several systems.
A current view of the measures that actually drive decisions.
DAT 02
Operational Reporting Hub
Teams export data into spreadsheets every week to recreate the same reports.
Repeatable reporting without the weekly spreadsheet ritual.
DAT 03
Knowledge Assistant
Policies, product information and internal knowledge are hard to search and keep current.
Answers grounded in the organization's own approved material.
DAT 04
Document Intelligence
Staff read contracts, forms, reports or PDFs to find and re-enter structured information.
Extract useful data and route the exceptions to people.
DAT 05
AI Workflow Agent
A repetitive process requires people to read context, make simple decisions and update systems.
Automate the routine path while escalating uncertainty.
03 · Project patterns
Most good projects start with one of five patterns
You do not need to arrive with a software specification. If one of these patterns sounds familiar, there is usually something worth examining.
The spreadsheet became a system
It started as a simple tool. Now multiple people depend on it, the logic is fragile and nobody wants to touch the formulas.
Typical path: Extend or Build
The core software is fine. The workflow is not
Your ERP or CRM does the important things, but staff still work around it for the process that matters day to day.
Typical path: Extend
The systems do not talk
Good tools exist on both sides, but employees copy data between them, reconcile exports or chase status manually.
Typical path: Integrate or Automate
Your workflow is actually different
The way you quote, schedule, deliver, transact or serve customers is part of how the business competes. Generic software keeps forcing compromises.
Typical path: Build
People are doing work software can coordinate
The task is mostly reading, moving information, checking rules, generating updates and escalating exceptions.
Typical path: Automate
04 · Example architectures
Custom does not have to mean replacing everything
The best architecture usually keeps proven systems of record and adds the operational layer the business is missing.
Contractor Operations Layer
For a construction or trades business that has accounting software but runs the rest of the operation across spreadsheets and disconnected tools.
- Keep the accounting system
- Add the missing operational workflow
- Connect estimate → project → purchasing → margin
Multi-Location Service Business
For a business where customers book services, staff manage capacity and leadership needs one view across locations.
- One rules engine for availability
- Customer self-service where it helps
- Operational data feeds reporting automatically
Enterprise Operations Layer
For a company with mature enterprise software that still needs purpose-built workflows, portals or automation around the edges.
- Protect systems of record
- Build around business-specific gaps
- Use automation where coordination is the problem
05 · Prioritize
Do the valuable things first
The best first project is rarely the biggest idea on the whiteboard. Start where measurable business value is high, the workflow is understood and implementation risk is manageable.
High value with manageable complexity is the useful zone: enough impact to matter, small enough to prove quickly.
Business value →Implementation complexity →
High-value quick winsStart here
Strategic investmentsPlan carefully
Low priorityDo not automate everything
Question the economicsComplex and low value
06 · Opportunity checklist
Signs you may have a systems problem worth solving
You do not need all of these. Two or three in a valuable workflow is usually enough to justify a closer look.
- Employees enter the same data more than once.
- A spreadsheet has become mission-critical.
- Customers call staff for information that could be self-service.
- Your ERP has the data but not the workflow.
- Staff copy information between systems by hand.
- Recurring reports require manual data preparation.
- Your process is genuinely different from the market.
- Important information is trapped in documents and PDFs.
- One person knows how the process works and everyone depends on them.
- A bad handoff regularly creates delay, rework or lost revenue.
Start with the workflow. Not the software
Show us the process that is slow, manual, disconnected or hard to scale. We will help determine whether the right answer is to integrate, extend, build or automate.