Bizzlogistix

Snapshot

What they do

Bizzlogistix is a freight brokerage operating as Ship BZX, arranging freight for shippers through direct relationships with the people inside distribution companies rather than through volume bidding. Transparent, scalable logistics partnerships is how they describe it themselves.

How they grew

A small, relationship-driven team whose growth has come from direct outreach and personal relationships rather than from a marketing engine — and who are now trying to multiply that without losing what makes it work.

Delivery

Co-delivered by Value-First Team and USS.

Where they started

Their outreach already worked. Direct, personal, well-timed contact had produced real relationships and a meaningful share of the revenue that grew the business — and none of it was recorded anywhere. No process was written down, no account was instrumented, and the motion that had produced the growth lived entirely in the heads of the people doing it. That is a business that is working and cannot yet be scaled, which is a different problem from one that is broken.

They had put a CRM in themselves a few months earlier. It could hold records; it could not run a process, and nothing in it could answer the question their whole business turns on — of all the accounts we could contact this week, which one has a reason to hear from us today.

What we delivered

A reframe of what they were buying. They came asking for lead generation. They already have lead generation — it produced the relationships that grew the company. What they lack is any way to see it, repeat it, or hand it to a fifth person. So the work was scoped as: make the motion repeatable, then visible, then AI-native, in that order.
A shape with the hours named per phase — decide, build, hand over, across six weeks, so they can see what lands in each and when visible progress arrives.
The costed, itemised list they originally asked for, folded into the first phase — and said plainly to be theirs to keep. They can stop at the end of phase one holding it and execute it themselves.
Time ring-fenced for the one thing that matters most, protected so it cannot be squeezed by the build: an account check that runs on its own and answers whether there is a reason to call an account today.
The costs that are theirs, named up front rather than discovered in week three — platform licensing, enrichment data, and sending-domain setup, each identified as a dependency rather than an upsell.
A gate in week one instead of a caveat. The targeting work depends on contact data existing for their segment, and coverage there is uneven. So the first thing on the calendar is a half-hour test of whether it does — beginning with the thing that could change the plan rather than the thing that would confirm it.
A risk named against our own interest. A CRM makes a motion visible and repeatable; it creates no outreach hours and finds no better accounts. Said in the proposal rather than discovered afterwards, so success is measured where it can actually be met.

What changed

The request arrived as a platform project — automation, AI setup, email configuration. It came back as a reading of what they already do well, and the work reordered around protecting it. That reordering is the substance: configure first and you automate a process nobody has written down, which is how a working business ends up with an expensive record of its own confusion.

The second thing to change was the definition of done. Not revenue, and not a promise of a first route. The stated exit condition is that their own team runs the motion without us, and that the pipeline is instrumented well enough that when a route does land they can see which account, which relationship and which touch produced it. Enablement over dependency, written into the proposal as the thing we are accountable for.