Field note. Opinion.

Buy, configure, or build.

Buy when a product already does the job and supports your data. Configure when a product is close and the gap is a report or a workflow setting. Build only when the job repeats, matters to your results or operations, and no supported product fits. Before building, name who will own the tool after the engineer leaves.

ChoiceWhen it fitsWhat must also be true
Buy.A product already does the job and supports your data.The license, the support, and the vendor's roadmap are enough.
Configure.A product is close. The gap is a report or a workflow setting.Someone on your team can own the settings after setup.
Build.The job repeats, it matters to results or operations, and no supported product fits.You can name who owns the tool after the engineer leaves.

Five questions before you build.

  • Does this job happen every event, or did it happen once?
  • What breaks on the weekend if nobody does it?
  • Did you ask the vendor? A missing export is often a support ticket.
  • Who runs the tool when your data engineer changes teams?
  • What does the next rule change or logger change cost you?

Yes, we sell custom work. Most jobs still should not be custom. A tool nobody owns becomes the next thing your team does by hand. If a product fits, we will tell you to buy it.

A one-off job with a tolerable manual cost may not need software. Compare the license or build cost with configuration, updates, support, and the person who will own the workflow. An unavailable vendor export is a support question before it is a build project.

For recurring work, inspect session reporting or radio review. Use the data-handoff worksheet to record unknowns before a quote.

Read the handover checklist

FAQ

Short answers.

When should a race team build custom software?

Only when the job repeats every event, matters to results or operations, and no supported product fits. Before building, name who will own the tool after the engineer leaves.

When is configuring enough?

When a product is close and the gap is a report or a workflow setting that someone on the team can own after setup.

Should a team ask the vendor first?

Yes. A missing export or report is often a support ticket, not a build.

BoxNext step

Not sure which one you need?

Fifteen minutes. No deck. A straight answer.