Real problems. Solutions that work.

FAQ

Questions, answered in plain English

A few things people ask before reaching out — no jargon, no sales pitch. Still not sure about something? Just send us a note.

• What is it that you actually do, in one sentence?

  We build small pieces of software that take repetitive, manual work off your team — the kind of tasks where someone is copying data between tools, answering the same questions over and over, or chasing updates. Sometimes that's a quiet “automation” running in the background, sometimes an “AI agent” that handles requests for your team. You describe what slows you down; we ship something that handles it.

• What's the difference between an “automation” and an “AI agent”?

  An automation follows fixed rules — when X happens, do Y. Example: every new order becomes an invoice in your accounting tool, no thinking required. An AI agent handles work that needs judgement — reading a customer email, deciding which department it belongs to, drafting a reply. We use whichever fits the job, and often both together.

• You mention “RAG” and “agents on your data”. What does that actually mean?

  It means an AI assistant that answers using your documents instead of guessing from the public internet. We feed it your policies, contracts, product docs, or knowledge base, and it replies only from those — with sources you can check. Your team and customers get correct, up-to-date answers without anyone having to memorise the manual.

• Do I need to be technical to work with you?

  No. You bring the problem — “our team spends three hours a day moving data between two tools” — and we handle the rest: choosing the technology, building it, testing it, and explaining it back in plain language. You stay in control of the outcome; we handle the wiring.

• What does “works with your stack” mean in practice?

  “Stack” is just shorthand for the tools your team already uses every day — Slack, Notion, HubSpot, Google Drive, your CRM, your shop, your accounting system. Instead of asking you to switch to something new, we plug into what you already have so the new automation feels like a natural extension of your current setup.

• What is “on-prem” or “hybrid” delivery, and do we need it?

  On-prem means we install everything on your own servers or private cloud, so your data never leaves your environment — useful in healthcare, finance, legal, or anything sensitive. Hybrid means part runs on your infrastructure and part on managed services. Most clients don't need this; if you do, we can deliver it.

• How long does a project take, and how much does it cost?

  Most first projects ship in weeks, not months. We start with a free conversation, scope the work concretely, and give you a clear quote — priced to what we actually do together, not a package rate. No open-ended retainers and no hidden subscriptions. You see a working result before committing to anything bigger.

• What happens after launch? Are we on our own?

  No. We monitor what we've built, fix anything that breaks, and adjust as your process changes. You can keep us on for ongoing support, ask for a one-off change later, or bring it fully in-house — the work belongs to you, not us.

Still have a question? Talk to us