Independent technology studio

Software for the bits of your business that have become a mess.

Spreadsheets, shared inboxes, and follow-ups that live in someone’s head. QIIQ replaces that tangle with a small system designed around how the work actually happens.


The usual shape of the problem

None of those individual steps are necessarily bad.

A form, an inbox, a spreadsheet, a reminder — each one made sense when it was added. The trouble is what happens between them: an enquiry lands, gets forwarded, gets logged (sometimes), and then depends on someone remembering.

A typical messy enquiry process
  1. Website enquiry
  2. shared inbox
  3. someone forwards it
  4. spreadsheet
  5. someone remembers to follow up

What QIIQ builds

Small internal systems, shaped around the process you already have.

The work is usually something staff already do by hand — enquiry handling, follow-ups, the status of a job — made into a system that is simple enough to actually use.

  • Enquiry trackers So a new enquiry has an owner, a status, and a next step — instead of sitting in a shared inbox.
  • Lightweight CRMs Enough structure to know who is in play, without dragging a sales platform into a business that does not sell that way.
  • Workflow tools The sequence of work made visible: who has it, what happens next, what is blocked.
  • Follow-up systems Reminders that belong to the process, not to whoever happened to see the email.
  • Operations dashboards A picture of what is waiting, overdue, or quietly stuck — drawn from the work itself.
  • Internal portals A place staff actually use, instead of another spreadsheet copy on someone’s desktop.
  • Integrations Connecting the two or three tools you already have, so people stop re-typing.
  • Reporting Simple answers to “what happened this week?”, without exporting to yet another sheet.

Working with QIIQ

Start with the process, not with a piece of software.

QIIQ does not begin by recommending a tool from a list. First comes what currently happens — including the unofficial bits, the workarounds, and the step that only one person knows.

  1. 01

    Understand

    Look at the real sequence of work, not the version in the procedure document.

  2. 02

    Simplify

    Strip it back to what actually matters, and drop the steps that only exist because of the tools.

  3. 03

    Build

    The smallest useful system — something staff can use this month, not a future platform.

  4. 04

    Support

    Adjust it once it meets real use. Processes change; the system should be allowed to as well.

Illustrative example

Independent clinic

A clinic taking new enquiries by web form and email. They land in a shared inbox. Whoever sees them first might reply. There is a spreadsheet of “people who got in touch”, usually a week behind.

A clearer enquiry path for the clinic example
  1. New enquiry
  2. assigned
  3. contacted
  4. follow-up
  5. booked / lost

Staff then have one place to see what has arrived, who owns it, what needs doing next, and whether it booked or was lost.

A system of this scale might typically be around £1,500–£2,500, depending on the workflow. This is an illustration, not a quote.

Plenty of SMEs are stuck in a gap: generic software that does not quite fit, spreadsheets that have gone too far, and “proper” systems that would be expensive and slow to impose on a process that is actually quite specific.

The useful move is often a straightforward system that matches the real work — and is allowed to stay small.

Most initial business-system projects are around £1,000–£3,000. Where QIIQ looks after hosting and upkeep, managed support starts at £99/month.

Business systems, including typical costs

Also: QIIQ Home

Smart homes that don’t require becoming a full-time Home Assistant hobbyist.

QIIQ also helps with Home Assistant, dashboards, automations, energy monitoring, cameras, heating, networking, and getting devices to talk to each other. Setup and configuration — not electrical installation.

QIIQ Home

Tell me about the bit of your business everyone complains about.

A short note is enough. I’ll tell you whether it sounds like a QIIQ problem, and what a small system could do.