Question 1

How do we begin?

Accepted Answer

With a short call, then an audit. The call establishes whether the problem you have is one we are useful for. The audit is the first paid stage: we work inside your operations and come back with a written picture of where time is going and what to change first.

Question 2

Do we have to commit to the whole programme?

Accepted Answer

No. The audit stands on its own and is deliberately scoped that way. You end up with a report and a roadmap you could hand to any competent operations person, whether or not you continue with us.

Question 3

How long before we see anything change?

Accepted Answer

The audit takes one to two weeks and the architecture stage about one more. Visible change usually starts in the build stage, so four to six weeks from the first call in a typical engagement.

Question 4

Is our firm too small for this?

Accepted Answer

Below roughly ten people, a well-organised shared drive and one project tool usually beat anything we would build. We are most useful between ten and a hundred people, where informal process has stopped scaling but there is no operations function yet.

Question 5

We are not architects or engineers. Does this still apply?

Accepted Answer

Often, yes. The pattern we work on (project-based delivery, many stakeholders, documents that need versioning and sign-off) appears in construction, property development, consultancy and legal work. The vocabulary changes more than the structure does.

Question 6

We already have ClickUp and it is not working. Can you fix it?

Accepted Answer

Usually. A tool that is not working is rarely a tool problem; it is a structure problem the tool inherited. We audit first and often keep the platform you already pay for.

Question 7

Will this disrupt live projects?

Accepted Answer

Rollout is staged and old systems stay live until the new ones are proven. We do not migrate a running project mid-flight unless you ask us to.

Question 8

How much of our team's time will this take?

Accepted Answer

During the audit, a few hours across a handful of people. During the build, more from whoever owns operations, typically half a day a week. We do the work; we need access and decisions, not headcount.

Question 9

Do you work on site?

Accepted Answer

We are remote-first and work with firms in several countries. If a stage genuinely needs to happen in the room, we will say so and travel for it.

Question 10

Who owns what you build?

Accepted Answer

You do. Code, documentation and accounts are yours, in your infrastructure, under your billing. We hand over credentials and repositories at the end of the engagement.

Question 11

What happens if we stop working with you?

Accepted Answer

The system keeps running. That is the point of the handoff stage: documentation, role-based training and a clear escalation path, so continuing with us is a choice rather than a necessity.

Question 12

Are we locked into a specific tool stack?

Accepted Answer

No. We choose the tool that fits your team, not the one we are most comfortable in. Where we build custom software, it is standard, documented code any competent developer can maintain.

Question 13

Where does AI actually fit?

Accepted Answer

In drafting, summarising, classifying and triage: the places where a person currently starts from a blank page. It reviews and you approve, rather than the reverse. We add it where it earns its place and leave it out where it does not.

Question 14

Is our data safe if AI is involved?

Accepted Answer

We scope which data an automation can see before we build it, keep client-confidential material out of third-party models unless you have explicitly approved it, and document every integration so you know exactly what goes where.

Question 15

Can automation replace roles on our team?

Accepted Answer

That is not what we sell. In practice it removes the coordination overhead that stops people doing the work they were hired for. What you do with the reclaimed capacity is a decision for you, not us.

Question 16

What does an engagement cost?

Accepted Answer

It depends on scope, and we quote after the audit rather than before it. The audit is a fixed fee; everything after it is priced against the plan you have already seen and agreed.

Question 17

Do you offer ongoing support?

Accepted Answer

Yes, on a monthly basis, and it is optional. Some firms take a light monitoring arrangement; others keep us on for continued build work. Neither is a condition of the handoff.

Question 18

How do you measure whether this worked?

Accepted Answer

Against the baseline from the audit: time spent on manual coordination, how long a status update takes to produce, how much of a project's record lives in one place. We agree the measures before the build, not after.

The questions we get before the first call.

Getting started

Fit and scope

How we work

Software and ownership

AI and automation

Cost and support

Ask the awkward question.