Introduction

Most consultancies are deliberately vague about how they work. The process is described in broad strokes on the website. The pricing is available on request. The timeline is subject to scope. The deliverables are outlined in a proposal that arrives after a series of exploratory conversations that may or may not lead anywhere.

This vagueness is not accidental. It gives the consultancy flexibility and puts the prospect in a position of incomplete information during the commercial conversation. It is also, for most growing service businesses trying to evaluate whether to invest in operational systems, deeply unhelpful.

This article is a transparent walkthrough of exactly what happens when a business engages Castlane, from the first conversation to a live system. No vagueness. No subject to scope. The actual process, the actual timeline, and the actual investment ranges for the most common types of engagement.

Stage one: the Systems Consultation

Every Castlane engagement begins with a free 30-minute Systems Consultation. Not a sales call where a solution is pitched before the problem is understood. A structured diagnostic conversation.

The conversation follows a consistent format. The first five minutes establish the business context. What the business does, how many people are involved, what stage of growth it is at, and what has prompted the conversation. The next ten minutes are a systematic diagnosis of the six operational pillars: CRM and sales pipeline, operations and workflow automation, reporting and financial visibility, client experience systems, marketing infrastructure, and recruitment and talent systems. The goal is to understand which of these are functioning well and which are generating operational friction.

The following eight minutes discuss what properly structured systems in the problem areas would look like. Not a specific solution proposal. A description of what the operational environment would look and feel like with the right infrastructure in place. This is where most prospects first understand the gap between where they are and where a well-systemised business operates.

The final seven minutes cover next steps. If the diagnostic has identified a clear systems opportunity, the next step is a proposal. If more information is needed, a follow-up conversation is scheduled. If the timing is not right, the conversation is left open. There is no pressure to proceed and no obligation created by the consultation.

Stage two: the diagnosis and proposal

Within twenty-four hours of the Systems Consultation, Castlane produces a structured proposal. Not a template with a name and date changed. A specific document built around the diagnostic conversation.

The proposal has six sections. Client context, a short summary of the business’s current operational situation as understood from the consultation. System objectives, what the systems being proposed need to achieve in operational and commercial terms. Expansion pillars, which of the six Castlane pillars are included in the scope and at what implementation level. Scope of implementation, a specific description of what will be built. Delivery timeline, the sequence and duration of the build. And investment, the specific project cost and any payment structure options.

Most proposals are two to three pages. They are designed to be read in ten minutes and to answer the question of whether this is the right investment clearly enough that the decision does not require a follow-up call. If the proposal raises questions, Castlane is available to talk through them. But in most cases the consultation has done enough diagnostic work that the proposal reflects what the business already understands it needs.

The investment figures in the proposal are specific rather than ranges. By the time a proposal is produced, the scope is understood well enough to give a precise figure rather than a band. The only variable that changes the figure after the proposal is submitted is a significant change to the agreed scope.

Stage three: project kickoff

When a proposal is accepted, a Project Kickoff Email goes out immediately. It contains three things. A summary of what is being built, confirming the scope agreed in the proposal. A link to book the System Design Session, a working meeting where the specific requirements for each component are confirmed before any build begins. And a timeline overview showing the key milestones from kickoff to delivery.

The System Design Session typically runs sixty to ninety minutes. This is where the data model is agreed, the workflow logic is mapped, the user experience requirements are confirmed, and any open questions from the proposal are resolved. The output is a confirmed specification that the build proceeds from. Changes after this point are possible but add to the timeline and investment. Changes before it cost nothing.

Most clients find the System Design Session is where the real value of the diagnostic approach becomes clear. The questions asked during this session, and the answers they require the client to think through carefully, often surface operational assumptions that have never been explicitly agreed within the business. What exactly happens when a lead arrives. What the stages of the sales process actually are and what makes a deal move between them. What compliance documentation is required and when. The act of specifying a system forces the clarity that the system then makes permanent.

Stage four: the build

The build phase runs from the confirmed specification to a tested, deployed system. The duration varies by scope.

Bronze level implementations, structured spreadsheet environments and simple workflow systems, typically deliver in five to seven working days. The build is straightforward because the scope is defined and the technology is familiar.

Silver level implementations, custom CRM environments, bespoke reporting systems, and structured workflow designs, typically deliver in one to two weeks. The additional time reflects the custom design work required to build something that fits the specific business rather than adapting a template.

Gold level implementations, Power Apps applications, Power Automate automation builds, and Power BI reporting environments, typically deliver in two to four weeks. The build time reflects the platform complexity and the testing required to ensure the automation behaves correctly across all defined scenarios.

Platinum level implementations, multi-pillar infrastructure builds with full system integration, typically deliver in four to eight weeks. These are the most complex engagements and the delivery timeline reflects the architectural work required to connect multiple systems into a coherent operational environment.

Throughout the build the client is involved at defined checkpoints rather than being presented with a finished system at the end. The midpoint review confirms that the build is progressing against the specification. The pre-launch review provides the opportunity to request refinements before the system goes live.

Stage five: handover and embedding

When the build is complete and tested, the handover phase begins.

Handover includes a structured training session with the team members who will use the system. Not a feature walkthrough. A practical session where the team works through the actual processes the system supports, with Castlane present to answer questions and make real-time adjustments where the system needs refinement.

Every system delivered includes documentation. How the system works. What each component does. How to perform the most common administrative tasks. This documentation is written for the people who will use and maintain the system, not for a technical audience.

After handover, a support period begins. The length of the support period varies by implementation level. Bronze and Silver implementations include a fourteen-day support window. Gold and Platinum implementations include a thirty to sixty day support period. During this time Castlane is available for questions, minor adjustments, and troubleshooting as the team embeds the new system into their working practice.

Stage six: the ongoing relationship

Most clients move to a support retainer after the initial support period ends. The retainer model is designed for a business that wants its systems to continue evolving as it grows rather than being replaced every eighteen months.

Standard retainers sit at £150 to £400 per month and cover minor field changes, dashboard tweaks, troubleshooting, user support, and light optimisation. Premium retainers for Gold and Platinum clients sit at £300 to £600 per month and add workflow improvements, automation adjustments, and reporting updates.

The retainer relationship is where most of the longer-term commercial value of operational systems investment is realised. A system that is maintained and evolved as the business grows continues to deliver operational leverage. A system that is not maintained gradually drifts out of alignment with how the business actually operates and eventually stops being used.

If you are evaluating whether Castlane is the right partner for your operational systems build, book a free Systems Consultation. The consultation itself will tell you whether there is a genuine opportunity worth pursuing. Book here.