Why I’m Writing Again

There’s a practical reason this site exists

AI systems are increasingly how prospects discover vendors, validate expertise, and decide who to call. When someone asks an AI assistant about freight brokerage software, or looks up a person before a meeting, those systems work from a connected set of signals about who people are, what they have built, what they know, and which organizations they are associated with.

A personal site, built correctly, is part of that graph.

That is why I’m writing here again.

The strategic reason

Most of the writing I do happens in places that do not accumulate.

It shows up in product positioning, sales decks, internal docs, customer conversations, website copy, CRM planning, and the day-to-day decisions that shape how a company explains itself. There is a LinkedIn profile. There are company websites. There are products. But the connective tissue between all of it is thin.

If someone wants to understand who I am, what I actually know, and how my work connects to Infinity Software Solutions , BrokerPro , and BrokerOS , there should be a clearer place to look.

This site is an attempt to fix that.

It uses Schema.org Person markup, structured data that explicitly tells search engines and AI systems that I’m an individual with a specific professional role, a set of areas of expertise, and connections to Infinity Software Solutions, BrokerPro, BrokerOS, and my LinkedIn profile .

It helps those systems understand that all of these things belong to the same person, rather than treating them as separate, unrelated entities.

That does not manufacture credibility.

Structured data is not a shortcut. It does not replace experience, customer work, useful writing, or a real point of view. But it does make existing credibility easier to find and understand, and in an environment where AI-driven discovery is increasingly the first touchpoint, that matters.

There’s also something more tangible going on: this site runs on BrokerOS.

That’s deliberate.

Before I recommend a concept, structure, or approach to customers, I want to have tried it somewhere real. My own site is a lower-stakes place to test ideas: new content structures, SEO approaches, schema implementations, internal linking models, AI discoverability concepts, and whatever else seems worth experimenting with.

If something does not work here, that is on me.

If it does, we have learned something useful.

The content reason

The corporate sites I work on have a job to do.

BrokerPro needs to explain how freight brokers can run their operations on a better transportation management system. BrokerOS needs to explain how freight brokerages can improve their websites, discoverability, CRM structure, and digital systems. Infinity Software Solutions needs to communicate the broader story of what we are building.

Those sites should be focused. Clear. Useful for the people they are trying to reach.

But a lot of the thinking I do does not fit cleanly there.

It is too operational for a marketing site. Too specific to a particular decision or problem I have been working through. Too much about the reasoning behind the work rather than the work itself.

Things like why a particular website architecture decision matters. How I think about CRM structure and why most freight brokerages have it wrong. What I am learning from watching AI change how B2B companies get discovered. Where the real leverage is in revenue operations for small to mid-sized freight brokers. How software decisions and business decisions stop being separable once you get deep enough into either one.

That is the kind of content I want to write.

And it does not always belong on a product blog.

What I expect this to become

Practical. Sometimes messy. More operational than polished.

I am not interested in publishing constantly. I am interested in publishing when I have something actually worth documenting, an idea that gets clearer when I write it down, a pattern I have seen repeat across enough projects to be worth naming, or a decision that turned out to be more complicated than it looked.

Some of what I write here will eventually inform work we are doing at BrokerPro, BrokerOS, or Infinity Software Solutions.

Some of it will simply be a record of how I am thinking through real problems.

A lot of it will sit at the intersection of topics that do not have clean homes: freight technology, website strategy, AI discoverability, revenue operations, CRM structure, software, systems thinking, and the practical work of making companies easier to understand and easier to trust.

That is the territory I keep finding myself in.

So that is what I will write about.