Bespoke business systems, designed around how your team works

For UK businesses with 10 to 250 staff that have outgrown the spreadsheet.

We build eight kinds of system. Most businesses start with one, usually the process that takes up the most time, and add the next once it is working. Every system connects to the tools you already use, runs on Cloudflare, and belongs to you.

  • CRM

    A CRM shaped around how you actually win and keep customers, with every email, call, and deal in one place.

    1. Enquiry loggedThe system
    2. Company details added from Companies HouseAutomated
    3. Owner follows it upA person
    4. Every email filed against the recordAutomated
    5. Pipeline updatedThe system

    What a build usually includes

    • Contacts, companies, and deals in one place, with the stages your team actually uses
    • Emails from Microsoft 365 or Google filed against the right record
    • Company details filled in from Companies House
    • Pipeline reports without a spreadsheet export
  • Invoicing and payments

    Invoices that go out on time, chase themselves politely, and land in Xero without anyone retyping a thing.

    1. Work recordedThe system
    2. Invoice raisedThe system
    3. Reminder sent on scheduleAutomated
    4. Payment plan agreedA person
    5. Payment matched in XeroThe system

    What a build usually includes

    • Invoices raised from the work, timesheets, or contracts
    • Reminders on a schedule you set, stopped as soon as a payment lands
    • Supplier invoices coded and sent to the right person for approval
    • Invoices and payments kept in step with Xero or QuickBooks
  • Onboarding

    New starters, role changes, leavers, and new clients taken through every step, with nothing slipping through.

    1. Offer acceptedA person
    2. Joiner record createdThe system
    3. Forms and signatures requestedAutomated
    4. Manager checks the documentsA person
    5. Ready for the first dayThe system

    What a build usually includes

    • One link for forms, documents, and signatures
    • Tasks for IT, HR, and managers created as soon as someone is hired
    • Role changes and leavers handled with the same care as joiners
    • New clients taken through identity and anti-money laundering checks
  • Screening

    Right to work, DBS, references, and identity checks ordered, chased, and recorded in one place.

    1. Checks orderedThe system
    2. Sent to an accredited providerThe system
    3. References chasedAutomated
    4. Decision signed offA person
    5. Result and expiry date recordedThe system

    What a build usually includes

    • Right to work checks through a certified identity provider
    • DBS, Disclosure Scotland, and AccessNI checks ordered through accredited providers
    • References requested and chased automatically
    • Expiry dates and follow-up checks tracked, with reminders before they fall due
  • Compliance

    Policies, training, registers, and data requests, with the evidence ready before anyone asks for it.

    1. Policy issuedThe system
    2. Reminders sent before the deadlineAutomated
    3. Read and acknowledgedA person
    4. Evidence kept on fileThe system

    What a build usually includes

    • Policies issued and acknowledged, with a record of who read which version
    • Training and CPD records with renewal reminders
    • Registers for incidents, complaints, and conflicts of interest
    • Subject access requests logged against their one-month deadline
  • Workflow automation

    The repetitive admin taken off your team's plate, inside the tools they already use, with a person approving what matters.

    1. Document arrivesAutomated
    2. Read and filedAutomated
    3. A person approves itA person
    4. Every step loggedThe system

    What a build usually includes

    • Approvals that reach the right person, with reminders and a record
    • Information moved between systems without copy and paste
    • Documents read and filed, with AI only where it saves real time and a person checking the result
    • Alerts when something stalls
  • Spreadsheet replacement

    The spreadsheet everything depends on, rebuilt as a proper system without losing what makes it work.

    1. What the spreadsheet does, written downThe system
    2. History importedThe system
    3. The team checks the numbersA person
    4. Live, with permissions by roleThe system

    What a build usually includes

    • What the spreadsheet does mapped and written down before anything changes
    • Microsoft Access databases and Excel macros rebuilt as web systems
    • History imported and checked against the original
    • Permissions by role, so people see what they need and nothing else
    Microsoft Access replacement
  • Integrations

    Your accounting, email, and payment tools talking to each other, so nothing gets typed twice.

    1. Payment taken in StripeThe system
    2. Sync runs, with retriesAutomated
    3. Xero updatedThe system
    4. Alert if anything stallsThe system

    What a build usually includes

    • Xero and QuickBooks for accounts
    • Microsoft 365 and Google Workspace for email, calendars, and documents
    • Stripe and GoCardless for card payments and direct debits
    • Companies House, HubSpot, and most other tools with an API

What to expect when you replace a process with a system.

No. Most businesses start with the one process that costs the most time and add to it once it is working. Each system is built to connect to the next.

Not answered here? Tell us about your process

Tell us which process takes up the most of your team's time

Five short steps, or a few lines by email: what the process is, who does it, which tools it touches, and where it goes wrong.