Hola! Here in The Untethered Flow I’ll occasionally be sharing some of my offerings for small business and nonprofit leaders. If these aren’t for you, feel free to skip them—or unsubscribe anytime if my work no longer serves. No te preocupes. 🩵

I’m an AI Third Bird. Not a Level 12 Gozar power user (though I’ve automated enough repetitive cognitive-load stuff to help me focus more on things that matter most) — and not the other camp either, the rabidly anti-AI contingent. I’m somewhere in the middle, using what works, staying curious, wanting a more sane, more ethical, less billionairey version of the AI ecosystem.

The AI tools marketplace is enormous, and finding the combo of tools that actually fit how you work can be harder than it sounds. But that’s symptom-level. The harder problem is infrastructure. The frameworks that live in one person’s head are the institutional memory that walks out the door when someone leaves. The accumulated thinking that should be powering everything, that’s not powering a sustainable system.

That problem doesn’t start at the org level. It starts with the people running them. Including me.

has been framing this idea beautifully in a different way for some time now:

Colonial time keeps you producing forward, never integrating backward.

Meaning, the output pile grows — and your systems should hold that, make it usable, searchable, yours (or the engine of your org) — never gets built. That’s true inside orgs and it’s true of the people building them.

K’iinBody is the system Ixchel built to fix it — and the K’iinBody Build Weekend, June 5–7, is where we build it with you.

Join the K’iinBody Build Weekend →

Here’s what’s included in the system that we’ll build with you side-by-side:

K’iinBody in Obsidian

A locally stored second brain. Your data lives on your machine, not someone else’s platform. Notes, drafts, frameworks, finished work — all in one place, actually yours.

The Stellar World Code

A skills-mapping framework (forked from work by Corey Haines and Paul Scrivens) rebuilt through your personal cosmology: astrology, Human Design, and lineage woven into the architecture. Eight load-bearing elements that map what you do, how you do it, and where it came from. Not a one-time setup — a live architecture that keeps informing how your system grows with you, that is uniquely mapped to you.

Content Dashboard (optional add-on)

A planning and publishing layer built directly inside your system. Your content ideas, drafts, and publishing calendar live in the same place as your frameworks and body of work, connected to the Stellar World Code that already knows how your mind works.

The Stellar World Code and Content Dashboard are what make K’iinBody different from other Second Brain offerings. You might have seen before. It’s not a template you fill out once. It’s a live map built specifically around your cosmology and ways of working, and it keeps shaping how your system evolves.

I’ve been running on it every day. Honestly, I’m smitten with it. I’m biased, but coming from someone who spends most of their time inside geeking out over people’s broken systems, K’iinBody feels like medicine.

K’iinBody is Ixchel’s creation — they built the system and designed the Stellar World Code. I’m joining the weekend as a co-facilitator, bringing an ops and systems design lens to help support what you build in real time.

Limited to 10 spots to make this a massively personalized Done With You weekend (plus we support you for 30 days afterward).

If any of this is landing, and your body of work deserves an actual home, we hope you’ll join us!

Join the K’iinBody Build Weekend →

Saludos,
Jaimey

Hola, I’m Jaimey — founder of Bearfuht Labs. I work with impact-focused small businesses and nonprofits on ops and systems: right-sized infrastructure that gets out of your way and lets your people focus on the work they’re actually here to do.

If any of this landed, DM me, drop a comment, or book a no-strings virtual coffee.

I have a colleague and potential client whom I was talking to recently, about upgrading her business and project ops systems across her three business divisions.

When she told me, “Oh, we’ve used Asana and Monday before, but I never understood how to use them,” that told me so much. Not about her, but about whatever consultants were in her life and business in the past.

I’m a consultant. I LOVE to build and repair ops and project systems for purpose-driven SMBs and organizations. And I need to say something uncomfortable about my industry: too many in our industry are taking your money, building systems you can’t maintain, and walking away way too quickly.

Off the shelf project or operations systems without any human-to-human care after you buy the thing create more friction for our clients than they fix, period. It’s a disaster recipe we need to call out, a thing we need to slay.

This open letter isn’t about trashing other consultants. It’s about seeing and helping overloaded small business leaders like you triage and trust what good, supportive work and systems can look like.

Subscribe now

It’s Not a Tool Problem. It’s an Abandonment Problem.

Raise a hand if this sounds familiar:

• A consultant shows up, excited about their framework. They sell you a solution.

• They build you something that looks impressive in the demo.

• They hand you the login and disappear.

• Six months later, your team is back on whatever outdated or dysfunctional system you used before. You revert back to what was familiar or comfortable.

And maybe you think:

Maybe we just need a different tool. Maybe Asana wasn’t right. Maybe ClickUp will work better. Maybe we’re just not disciplined enough.

Stop.

You don’t necessarily have a tool problem. You might have a consultant problem.

Here’s what’s actually happening:

❌ The system wasn’t built for your workflow — it reflects someone else’s ideal process, not how work actually moves through your team

❌ No one showed you the why, only the what — you got a tour of features, not an understanding of the logic that makes it work

❌ You’re still the one running everything — the system didn’t free you up to lead, it just gave you another thing to manage and troubleshoot

❌ Your team can’t see the value — if it feels like extra work instead of less friction, they’ll abandon it the second you stop watching

❌ The consultant disappeared when you needed them most — no transition support, no “call me if it breaks” safety net, just radio silence

If this has happened to you in the past and it’s scarred your trust, I’m sorry. Chances are, the consultant was more focused on delivering their framework than solving your problem, and that’s a shame.

When what you actually need is someone who designs for the team you have, trains your people to use it, and sticks around long enough to make sure it works. The relationship with you doesn’t stop at the “it’s built” stage.

Three Thinking Errors That Keep You Stuck

These aren’t the only ways founders get trapped in the system-adoption cycle, but they’re three common, fixable ones:

“We just need the right tool”

You’ve tried two, maybe three platforms. Each time it felt promising—then your team stopped using it. So you think: *Maybe this tool just isn’t the right fit.*

What’s actually true: The tool isn’t the problem. The implementation is. Every system you’ve tried probably *could* have worked—if someone had built it for how your team actually operates, not how a consultant thinks teams “should” operate.

“This is just how consulting works”

You think: *“Consultants build the thing and leave. That’s the deal. We’re supposed to figure it out from there.”*

What’s actually true: That’s not a good, healthy consulting relationship. Good consulting doesn’t end when the system is built. It ends when your team can use it without the consultant in the room.

“If it’s not working, we must be doing something wrong”

Your team won’t adopt the system. Tasks aren’t getting updated. People keep defaulting to old habit and systems. And you think: *“Maybe we’re just not disciplined enough. Maybe our team isn’t good at following through.”*

What’s actually true: If your team won’t use the system, it’s not necessarily a discipline problem, but a design problem. A good system meets your team where they are. It reduces friction and welcomes ease, not the other way around.

A Healthy Consulting Partnership Should Look Like This

Here’s what’s different when you work with someone who’s invested in your success and growth long after they’ve finished working with you:

Right-sizing: They build for the team and resources you have, not the team you aspire to grow to. They ask what you actually need *right now*—and build that, with room to grow later.

Personalization: They adapt the system to how your team already works. They don’t impose a rigid framework and expect you to contort around it. They observe your habits and design *with* them, not against them.

Co-creation: You’re in the room. You understand the logic, not just the output. When they’re done, you don’t just have a system—you can explain it to someone else.

Leadership freed from the “operator” hat: You get visibility into what matters—where projects are, what’s blocked, what needs your attention—without you becoming the person who manages the system.

Built to feel good, now and later: The system doesn’t just function—it feels sustainable to work in. Six months from now, a year from now, your team still trusts it because it was designed with whole humans in mind, not just productivity metrics.

Handoff with care: The consultant sticks around for the handoff. Maybe that’s a week. Maybe it’s 30 days. Whatever. But it comes with training, walkthroughs, documentation that makes sense, and a window where they’re accessible for lingering questions. They don’t ghost you the day the system goes live.

It’s what you deserve.

What I Do Differently

I specialize in systems that teams actually adopt because they’re designed for how work happens in your business and are capacity-aware—built with whole humans in mind, with room to flex for “holy shit” moments and rest.

I don’t hand you a framework and disappear. I co-create with you, train your team, and make sure you can maintain what we build long after I’m gone.

For quick setups: My Unjammed Ops: QuickStart offering gets you a ClickUp or Asana system up and working in 1-2 weeks, with handoff care built in.

For deeper partnerships (retainer work, custom builds, strategic roadmapping): We start with an Audit + Action session—90 minutes to map your workflows, identify friction points, and build a clear roadmap. If you move forward, the session cost applies to the project. If not, you still walk away with a useful audit report.

This is what responsible, supportive consulting looks like:

• Systems right-sized for your team today and your future trajectory

• Training so your people know how to use it (not just tolerate it)

• Clear documentation you can actually reference

• Post-launch support without abandonment

If you’ve been burned by a consultant who built something you couldn’t maintain, I need you to hear this: It wasn’t your fault.

The system failed you. The consultant who didn’t set you up to succeed? They failed you, too.

But here’s the good news: it’s all fixable.

You can have systems that actually work—systems your team will use, that you can maintain, that make operations easier instead of harder.

Ready to build something that actually sticks?

Reply to this, DM me, or head to bearfuht.com to book a no-strings discovery call. We’ll talk through what’s broken, what you actually need, and whether we’re a good fit to work together. No pressure, no pitch—just clarity.

Share