Why Visual Tracking

See whether Visual Tracking fits how you work

This page helps you decide, not sell you. Visual Tracking solves a real problem for project-based manufacturers on Business Central, and we are honest about who it is for and who it is not.

Visual Tracking fit assessment

Is Visual Tracking for you?

Visual Tracking is built for a specific kind of company. There are four parts to it, and the more of them you have, the better the fit.

  • You are a project-based manufacturer. Engineer-to-order, make-to-order, or heavy fabrication. Each job is its own thing, not a unit on a high-volume serial line. Construction, marine, and oil-and-gas project work also fits.
  • You already use Business Central as your ERP. Visual Tracking is a Business Central extension. It does not run anywhere else.
  • You use the Business Central Manufacturing module. Production orders, BOMs, routings, work centres. If you bought Business Central for finance and inventory only, Visual Tracking has nothing meaningful to attach to.
  • You use the Business Central Project (Job) module. At minimum, you create a Job record per project and tag posted entries against it.

Strong-fit signals

When these are present, the adoption usually goes smoothly:

  • Project Managers exist as a named role with budget tracking in their job description.
  • Budgets are tracked per project today, even informally (Excel-per-project counts).
  • Items can be classified by project, even partly: a naming convention, item categories, or production history.
  • Work centres are set up with discipline. Each one has a clear account type (hours-cost, sales, subcontracting purchase).
  • Two or three Project Managers can commit four weeks of pilot use alongside their existing tools.

Weak-fit signals

When several of these are present at once, Visual Tracking is probably not the right tool. We will say so when we talk.

  • High-volume serial production. Every unit is identical. There are no projects to attribute budget to.
  • The ERP is not Business Central, or Business Central is used for finance only with manufacturing kept outside the system.
  • The Business Central posting flow has been heavily customised in ways that would conflict with the subscribers Visual Tracking installs.
  • No appetite for a four-week pilot. “We want it live for everyone on day one” is the single most common reason adoptions stall.
  • No clear project sponsor. Decisions that should take minutes will take days.

The full qualification rubric is the Customer Fit guide we share after a meeting. The shape above is the public version.

What makes us different

Six things, each with a one-line proof.

For Business Central administrators

Visual Tracking is a per-tenant Business Central extension, delivered via AL-Go for GitHub. It installs into your tenant using standard extension deployment; the data lives where your Business Central data already lives.

The extension subscribes to standard Business Central posting events (Sales-Post, Purch.-Post, Item Jnl.-Post Line) and tags new posts automatically. There is no scheduled job, no cron-driven ETL, and no second database to reconcile.

If your environment has invasive customisations on the same posting events, that is the one thing worth checking. A sandbox install before production usually settles the question. We can review your subscriber list on the call.

Document attachments live in your own Azure Blob Storage account. Configuration is a one-time admin task at install, described in the Azure Blob Storage estimation guide and our onboarding kit. Typical running cost is under $20 per month on the LRS Hot tier.

Wonder if it is for your company?

Book a meeting and we will walk your Business Central environment, the module to lead with, and whether Visual Tracking earns its place. If it is not a fit, we will say so.

Product updates worth reading

A short email when we ship something useful for shop-floor teams.

You can unsubscribe anytime. By subscribing you agree to our Privacy Notice.