The Case for Hiring a Notion Guru

If there is a spectrum of software, the Claude Codes of the world sit at the exciting end of it. By contrast, one would never use that term to describe an enterprise resource planning systems. It's not all about sexy, though. Good luck running a firm without reliable payroll, benefits, accounts receivable, and accounts payable applications.

I know more about ERP systems than most. For more than a decade, I made my bones as an enterprise systems consultant. New back-office systems don't implement themselves. As I write in Why New Systems Fail, organizations have always needed seasoned folks to do for this critical job. Great, but which individuals?

Independents usually possess deep domain knowledge, but CXOs tended to view them as risky because the certification game remains alive and well. As the old maxim goes, “Nobody ever got fired for hiring IBM.” A partner's letterhead provided cover in case things broke bad.

And they often did.

My ERP days are long behind me, but not much has really changed.
These implementations are still massive in scope. Expect multi-million dollar engagements, year-plus timelines, and large teams. (Ditto for delays and organizational politics.) No single person—no matter how accomplished, versatile, or intelligent—could independently handle a gig of any consequence.

The Increasing Viability of the Solo Practitioner

For the last few years, Notion has been the focus of my development efforts. The popular, incredibly powerful tool has evolved considerably since I began using it in 2020. Foolish is the soul who views it as a note-taking app.

Make no mistake, though: the most daunting Notion project is far less complicated, time-consuming, and expensive than the simplest ERP implementation. Apples and coconuts. As a result, in the Notion universe, engaging a solo developer or consultant is far more common than in its ERP equivalent. Here are five reasons that firms in need of Notion expertise may prefer to engage a skilled and knowledgeable independent over a dedicated agency.

Steve Jobs, AI, and the 100X Quote

You may have heard the old Steve Jobs' quote, “The difference between the average software developer and the best is 50 to one; maybe even 100 to one.” Whether that statement has ever held water is anyone's guess, but the following facts are indisputable:

• Not all consultants and developers are created equal.
• Rock stars who have mastered AI and other automation tools are considerably more productive than those who are still dipping their toes in the water.

Brass tacks: significant constraints always limited what even the most talented individuals could realistically accomplish. Those boundaries haven't entirely disappeared, buy they have certainly eroded in the last few years.

Streamlined Sales Process

Working with me is straightforward. I can't envision a simpler process.

Even a three-person team can confuse who is supposed to do what when.

That's not to say, though, that bottlenecks don't occasionally emerge. A great deal hinges upon the organization hiring me. Some have pulled the trigger immediately after our discovery call. Others have dragged out the process for months.

No Box of Chocolates

My clients know that if they hire me then they'll get me. That is, I'll be the one asking the questions, gathering the requirements, explaining Notion's inner workings, building the databases, recording training videos, and setting up the workspace automations. Put differently, they won't get:

• A consultancy's B- or even C-team.
• A blended group of junior developers or consultants effectively learning from their senior counterparts while on the client's dime.
• The next available consultant or, if you like, whoever happens to currently be on the beach. (Cue obligatory Forrest Gump quote.)

I've seen all of these scenarios play out first hand. Things get ugly quickly.

Direct Communication

Even at boutique firms, different layers and communication styles can complicate effective collaboration. Issues can arise when:

• A person forgets to CC someone else on an email.
• Someone fails to follow protocol.
• A key team member goes on vacation and forgets to set her email auto-responder or Slack status.
• Person X suddenly exits the organization. Critical organizational knowledge leaves as well—permanently.

In my experience, the more people involved in a project, the more problematic the communication and the greater the chance for misunderstandings.

Notion Formulas Based on Attachments

Impossible? Think again.

Phil SimonPhil Simon

Unequivocal Accountability

All else being equal, there's far less finger-pointing and a more intense CYA mindset at smaller firms than at larger ones. I've worked for both. It's not even close.

Don't conflate less with none, though. Even a three-person team can confuse who is supposed to do what when.

Feedback

Do recent AI advances make you think differently about hiring an expert vs. a small team?