A PRACTICAL GUIDE / BUSINESS SOFTWARE

Should you use existing software or build a custom tool?

For a small business, the answer might be a feature you already pay for, an off-the-shelf app, or a custom tool. Here's how I compare the options.

THE SHORT ANSWER

Start with the task your team needs to finish.

Use an existing feature or a ready-made app when it handles the task without costly workarounds. Connect tools when the handoff creates extra work. Consider a custom tool when your team needs a shared view or action the available software can't provide. Weigh the improvement against setup, build, and ongoing costs.

Compare the three options

CHOOSE THE APPROACH

What would solve the problem?

Take one task your team repeats. Compare how each option would handle it, including the steps people would still have to do.

Use ready-made software.

Your current software—or another off-the-shelf app—handles the task without much manual work.

FOR EXAMPLE

Use a built-in report instead of commissioning a dashboard.

What to check: Confirm the features and access you need are included in the plan, and test with your team.

Connect the tools.

The tools work on their own, but someone keeps copying information or passing requests between them.

FOR EXAMPLE

Send a form submission into your team's task list with the right details attached.

What to check: Connections can fail. Someone needs to see errors and know what to do next.

Build the missing tool.

People need one place to see information, take an action, or follow a process your current tools don't support.

FOR EXAMPLE

Let vendors check their sales and stock, then book a restocking time in the same portal.

What to check: A custom tool needs testing, upkeep, and a clear owner. Include those costs in the decision.

Not sure which fits? Show me one task and the tools your team uses. We can talk through what to check next.

Talk through your options

Free · 20 minutes

TRY THE REAL TASK

Check these before you commit.

A feature list won't tell you how much work will remain. Walk through the task with the person who does it, using information from a normal week.

  • Can it handle a real workday?

    Try a normal task and an awkward one: a missing record, changed request, or duplicate entry. Check the result with the person who will use it.

  • What is the full cost?

    Include setup or build costs, subscriptions, training, support, and the work that remains. A lower monthly price can still leave the team doing hours of manual work.

  • Who can see and change things?

    Check access for staff, vendors, and customers. A useful tool still needs to keep each person's information and permissions straight.

  • Can you get your information out?

    Check exports, account access, and what happens if you change providers. For a custom build, agree on source code, documentation, and ownership in the proposal.

BUILD AROUND WHAT WORKS

You may only need to fill one gap.

A custom tool can sit beside what you already use. Keep recording sales in your sales system; build a dashboard or portal around the information and actions your team needs.

I built these examples in businesses I help run.

  • One view of the business.

    I built Pulse to bring sales, advertising, and email into one view the founders check on their phones. I connected the data and checked it against the source reports.

    See the Pulse reporting dashboard →
  • One place for vendor tasks.

    I built the vendor portal for sales, stock, and restocking bookings. It replaced three separate weekly workflows, giving staff and vendors fewer steps to manage.

    See the vendor operations portal →

AGREE ON THE WORK

What would I quote?

Show me one report or task. I check the data, who needs access, and what your software can support. If a better setup solves it, I'll tell you.

When a build makes sense, the proposal covers the features, connections, access rules, testing, team handoff, price, timing, and ongoing costs. Custom dashboards and apps get their own scope and quote.

If you only need a workflow between existing tools, see how I price a first workflow build. That range isn't a price list for custom apps.

BEFORE YOU DECIDE

A few common questions.

When should I wait to build?

If the task rarely happens, no one agrees on the steps, or the cost outweighs the improvement, simplify the process first. This guide can help you choose a first task.

Do I need a paid audit before a custom build?

No. If the task is clear, we can scope the project after a free conversation. If several processes are tangled together or you're unsure what to fix first, we can discuss the Business Systems Audit. We agree on that step before booking it.

Does a custom tool need AI?

No. A dashboard, form, or portal may only need clear rules and reliable data. AI can help with reading, summarizing, or drafting when the task calls for it. I include human review where mistakes would matter.

Who looks after the tool once it's built?

We agree on who checks failures, maintains connections, and handles changes before the handoff. If you want ongoing help improving systems across the business, we can discuss a Fractional AI Operator retainer separately.

BRING THE TASK

What is your software making harder?

Show me the report, spreadsheet, or task your team keeps working around. We'll talk for 20 minutes, free, and look at whether a better setup, a connection, or a custom tool would help.

Talk through your options

Free · 20 minutes · Kansas City + remote