How we work

We start by mapping where leads, jobs, invoices, tasks, approvals, and client communications move today. Then we design connected workflows around the operational Spine and add AI only where it can help with context and approval.

Start with a discovery call

30 minutes. No commitment.

How we approach every engagement

A few principles that shape every engagement

Discovery before design

We never design before we understand. Every engagement starts with discovery: mapping your leads, jobs, invoices, approvals, client communication, and operating reality.

Design before code

You see and confirm the workflow design before anything is built. What gets built is what you agreed to, not an interpretation.

Phased delivery

We deliver in phases, not one big launch. You see value and give feedback before everything is built.

Continuous improvement

After launch, we stay. The environment evolves with your business — supported, monitored, and improved over time.

The process

Five phases. Clear outputs at every step.

Discovery

2–4 weeks

We learn how your business actually operates — not how you think it does, and not how a generic product assumes it does.

What happens in this phase

Workshop sessions with your team to map current workflows
Tool and data inventory — what you use, how it connects (or does not)
Pain point and friction mapping across each operating area
AI and automation opportunity identification
Team structure, roles, and access requirements

Output

Discovery report covering your operating environment, key challenges, and recommended scope for the first build phase.

Design

2–3 weeks

We translate discovery findings into a detailed operating environment design — modules, data model, workflows, AI moments, and interface concepts.

What happens in this phase

Operating environment architecture: modules, data model, user roles
Workflow design: stages, rules, automations, and decision points
AI feature design: where AI assists and what it does at each moment
Integration design: which existing tools connect and how
Dashboard and reporting design

Output

Design specification and interface concepts, reviewed and confirmed by you before any code is written.

Build

6–16 weeks depending on scope

We build in phases, starting with the highest-value workflows. Each phase is reviewed before we move to the next.

What happens in this phase

Phased build starting with your most critical workflows
Regular review sessions — you see and test each phase as it is built
Feedback incorporated before moving forward
Documentation written alongside the build, not after
Security and data handling built in, not added on

Output

A working environment built to the confirmed design, with your team involved at each phase.

Launch

1–2 weeks

We manage the transition from old tools and workflows to the new environment — minimising disruption and making sure your team is ready.

What happens in this phase

Data migration from existing tools and systems
Team training and onboarding — workflow walkthroughs, not just a manual
Cutover planning — who switches when and in what order
Parallel running period if needed to reduce risk
Post-launch monitoring for the first two weeks

Output

A live operating environment with your team using it confidently from day one.

Evolve

Ongoing

After launch, the environment keeps growing. New functions, workflows, AI tasks, dashboards, and integrations are added as your business needs them. This is not a one-off project.

What happens in this phase

Ongoing support: questions, fixes, and adjustments handled promptly
Monthly improvement review — what is working, what your business needs next
New functions, workflows, and AI tasks added as the business grows
Performance and reliability monitoring
Proactive identification of new operational AI opportunities inside your workflows

Output

An evolving operating environment that keeps adapting to your business — supported by a team that knows how you operate.

What the working relationship looks like

Transparent, responsive, and built around your operating reality

North Ark works as a close partner, not an arm's-length vendor. You have a named contact who knows your business, responds quickly, and makes decisions in your interest.

We communicate clearly about what is being built, when, and why. If something changes — scope, timeline, complexity — you hear about it from us before it becomes a problem.

We do not disappear after launch. The relationship is designed to improve your operating environment over time, not to hand you something and move on.

Regular touchpoints

Weekly or fortnightly check-ins during the build. Monthly improvement reviews after launch. Always accessible in between.

Nothing built without sign-off

Every phase has a review point before we proceed. You see what is being built and confirm it is right.

Your team is involved

We involve the people who will use the environment, not just the decision makers. Better adoption, fewer surprises.

Scope managed explicitly

Changes are classified as part of the agreed scope, a scope addition, or a future phase. No hidden scope creep.

What to expect

We are direct about what we are not

Another clunky SaaS tool or generic no-code platform

A team building an operational Spine for service businesses, then extending it with workflow modules for how revenue, delivery, and cash flow actually move.

A team that builds and moves on

A partner that stays, supports, and keeps evolving the operational Spine as your business grows.

A generic agency that takes any software project

A team focused on one thing: AI operations software for service businesses with connected vertical workflow modules.

An AI consultancy promising transformation through chatbots or dashboards

A team that embeds AI into real workflows where it prepares, checks, drafts, updates, estimates, and routes work with humans staying in control.

Common questions about working with North Ark

How long does a typical engagement take?: Discovery and design take four to seven weeks. The first build phase typically takes eight to twelve weeks. The full initial environment — including all core workflows — is usually live within five to six months. We work in phases so you see value earlier, not at the end of a long project.
Do you work with businesses outside of the UK?: Yes. North Ark works remotely and has delivered for clients in the UK, Europe, and beyond. Discovery and review sessions are conducted over video call. We work across time zones when needed.
What happens if our requirements change during the build?: Requirements change — that is normal. We classify changes explicitly: within agreed scope, a scope addition that affects timeline and cost, or a future phase item. You always know what a change means before we proceed. Nothing is absorbed silently and nothing is invoiced without discussion.
How do you handle support after launch?: Support is included in the ongoing engagement. Bug fixes and performance issues are addressed promptly. Improvement requests are reviewed monthly and prioritised together. We do not offer one-off project support — the relationship is designed to be ongoing.
Can we start small and expand?: Yes — and that is usually the right approach. We scope an initial phase that delivers the highest-value workflows and proves the model. Subsequent phases add to it. The environment is designed to expand from the start, so later phases fit cleanly onto what was built first.

Tell us where work slips between leads, jobs, and invoices.

Book a 30-minute discovery call. We will map your workflows, identify where AI could genuinely help, and show whether a connected operational Spine fits your business.

Book a discovery call

We will confirm your booking within 24 hours.