From agreement to a live pilot, without an IT project

Somebody always asks it right after the demo, usually the person who has to sign: how long before this is actually running? That's not a technical question. It comes from watching platform projects slide from one quarter into the next while the budget sits committed and the sales team keeps selling exactly what it sold before.

Between a signed agreement and a live pilot there is no technology project. What follows is what fits in that stretch, why you don't need a build to get there, and which decisions stay on your desk regardless.

Launch time is a commercial number, not a technical one

Connectivity margins keep thinning, and every week somebody else sits down in the advisor's chair in front of your SME customers. If standing up a security offer takes a full season, the window closes on its own: by the time you're ready, your customer has bought something from their IT supplier, and your rep has quietly stopped treating that conversation as theirs.

There's a second effect that gets less attention, and it's internal. Long projects change owners. The sponsor moves, channel priorities shift, and the pilot you promised your sales director turns into one line inside somebody else's plan. A short launch stays inside the conversation that started it, with the same people who put their name on it.

Speed here isn't about being impressive. It's about spending your sales team's patience on customer calls rather than on waiting for a platform, because the attention you get from a regional sales manager for a new offer is finite and it doesn't renew every quarter.

What happens between signature and pilot

Four steps, and none of them is a build.

• Agreement. Commercial terms, shared objectives, and the brand your customers will see. Nothing to approve on the technology side, because there's nothing to install.
• Co-design of the catalogue. This is the step that needs your people, product and pre-sales in the same room. Your actual services go into the platform, described in your words and priced with your list, so every risk the platform finds points at something you already sell.
• Pilot with a first batch of SME customers. You pick the accounts and a small group of reps. The lead generation co-worker builds the risk picture on each one, the sales co-worker prepares the four-phase brief (Prepare, Discovery, Objections, Close), and the calls happen for real rather than in a training room.
• Roll-out to the sales team. Whatever worked in the pilot opens up to the rest of the team and the rest of the base, at whatever pace you set.

You bring two things: the SME accounts you want to try this on, and the catalogue of services you know how to deliver. The platform brings the rest, from the signals on each account to the material your rep works from on the call. If the split looks lopsided, that's the point. The part that normally stalls a launch, building a security practice from scratch, isn't on either list.

That stretch, from signature to a pilot running on real customers, is where these projects usually die. Here it has no build in it.

What "no integrations" actually means

The platform sits on top of the systems you already run. It doesn't need a CRM hookup before it can start, and it doesn't ask the SME to install anything on their machines.

Signals on an account come from what's already visible from the outside and from questionnaires the customer fills in using plain language: exposed assets, software nobody has patched in a long while, credentials that turned up in a data breach, and the organisational answers no scanner can infer. That's what keeps the launch short. There's no queue of technical work to clear before the first risk picture on a real account exists.

In practice this buys you two things. You don't have to raise a ticket with your own IT to begin, and the pilot runs on live customers without anyone touching their systems, which spares you the slowest negotiation in the whole cycle: the one with the customer's IT supplier, before you've sold them anything.

What a short launch doesn't buy you

No technology project doesn't mean no decisions. Catalogue co-design is where the launch either speeds up or drags, and that part is yours: if the services you sell live in a file nobody has touched in a while, the session starts by tidying the list. Better to find that out on day one than during a third pilot.

Then there's habit, which is the slow half of any change in method. The platform is the quick part; a rep learning to open with a dated fact instead of a generic slide takes longer, and gets there one conversation at a time. The pilot earns its place here too, because what comes back from the field corrects the catalogue mapping and the objection handling before you open the thing up to the whole network.

Roll-out has no deadline we impose. Go region by region, or start with the segment where your catalogue is strongest and the conversation easiest. None of those choices depends on technical timing, which is the whole idea.

A short launch isn't a speed contest. It keeps the commercial decision and the field test inside the same window of attention: you sign, you load your catalogue, and soon after you have real calls to judge it by, with your customers and your own numbers. Everything after that is yours to decide.