the BladeStack story

A month of posts should’ve taken days.

They did everything right, a real brand and a real content team, and it still fell apart at the seams. Here is exactly what happened, and what changed.

Mik, Blade Turbines and BladeStack
meet Mik

From Blackhawks
to BladeStack.

Mik spent over fifteen years keeping helicopters in the air, running some of Canada’s largest fleets, including UH-60 Blackhawks. He co-founded Blade Turbines and runs it alongside BladeStack, both built to make life easier for operators on the ground.

We built the brand behind both, the identity for Blade Turbines and BladeStack, working as a small team with copywriter Steph Laffy. He had the brand, and the people to use it. Getting it out every week was the part that kept breaking.

Mik, Blade Turbines and BladeStack

the origin

He is the reason Nueform exists.

the problem

Every step waits
on someone else.

It’s four jobs, with rounds of feedback in between.
Then a week gets skipped, and starting again feels harder than starting did.

On paper, this was the plan

ideas1dcopy2ddesign2dedits1dship1d

A few days → a month of posts (~30)

In reality, this is what happened

1ddeciding+3d2dwaiting+4d3dreview+5d1dbusy+3d1d

~1 month · every stage waited on the next

This was them, before Nueform.

A month of posts should’ve taken a few days…

It took a month, even if he had all four covered. Talent was never the problem, the loop was. By month two, he got busy and it died.

Content stacks fail at the seams.

one system

Four jobs, now one system.

The chain that used to wait on itself now runs end to end. You say what’s new, and it carries the rest.

the old way

You say what’s new
↓ +3 days waiting
Someone finds the angle
↓ +4 days waiting
Someone designs it
↓ +3 days review
Someone posts it
one system

with Nueform

You say what’s new
It finds the angles
It designs the post
It posts for you

and it learns from your edits

the result

Stalled to
shipping every week.

  • Every weekPosts go out on schedule, without chasing anyone
  • On brandBy default now, no drift between hands
  • Time backHours returned to running the business
the feedback
[Placeholder for Mik’s quote] I don’t think about posting anymore. It goes out every week, it always looks like us, and I got my time back for the actual business.
MikBlade Turbines and BladeStack
the bottom line

Your brand, running every week, without the seams.

The same story, minus the waiting: the ideas, the writing, the design, and the posting all run as one system, on brand, every week.