The operations engine for efficient teams

Your business runs on a handful of processes that have to happen the same way every time. Track40 is how your team makes sure they do.

Start free trial See what it does

30-day free trial, no card required. Then US$12 per editor per month — viewers are always free.

A pipe of four phases, with cards in each phase moving from left to right Intake Review Fulfil Invoice

You’ve been missing the tool for the job

Most teams run their work on a patchwork. A spreadsheet someone keeps half-current. A chat thread that scrolls away. A folder of versions nobody quite trusts. Information goes missing between people. A customer rings up to ask where their order is, and the person who answers the phone has to put them on hold and go find out.

That isn’t a people problem. It’s a tooling problem.

Track40 puts each process on rails

Every process is a pipe: an ordered set of phases that work moves through. Every piece of work is a card — a client, a service request, a job to deliver, an employee to onboard, an invoice to chase. Whatever the work is, it travels the pipe from start to finish.

Each phase asks for the information it needs. Until those fields are filled in, the card can’t move on. That’s what keeps the work standard, run after run.

One question, every time you open a card

What needs to happen to move this card to the next phase? The phase tells you which fields it needs. The card tells you which ones are still empty. You fill them in, and the card moves on.

When the card moves on, everything the next team needs is already on it. Different teams can own different phases without information going missing between them.

A card opened up, showing filled-in fields and one empty required field that blocks the card from moving on Order #4827 Phase: Review Customer Acme Co Service Annual install Quote total $4,820 PO number required Delivery date 15 March Fill in PO number before this card can move on Move to Fulfil
Three people looking at the same pipe of three phases, one card per phase Sales Operations Accounts

Everyone works on the pipe

Your whole team works inside the same pipe. When the phone rings, anyone on the team can search for the card, open it, and answer plainly: “I can see we’re waiting on payment. Here are the details.”

Nobody has to chase three people to find out where something stands. The status is wherever the card is.

You don’t have to get it right the first time

Sketch the phases. Decide what each one needs to know to do its part. Run real work through the pipe and watch where it gets stuck. Change what needs changing, and run more work through.

Within a few weeks, the pipe matches how the work actually goes when it goes well. Nothing missing at the handoff. Nothing miscommunicated. No drama.

A repeating loop: set the pipe up, run the work, watch it, change what needs changing, run more work Set up Run Watch Change

Then let the routine work happen by itself

Connectors coming soon

Once the process is running steadily, make it lighter. Today you can fire HMAC-signed webhooks at your own services and use the generous API directly — and because a card already carries clean, validated data by the time it moves on, whatever you wire up gets the right information at the right phase. Native Zapier, Make and n8n connectors are coming soon, so the routine tasks someone used to have to remember — the confirmation, the invoice, the follow-up — will run on their own.

A pipe with two automated side-jobs running off it: an email firing off when a card enters Review, an invoice raised when a card enters Invoice Intake Review Fulfil Invoice Send confirmation via Zapier · soon Raise invoice via webhook

A worked example

Watch a workshop get off paper

From a grease-stained job sheet to “ready by five tomorrow” in eight seconds — the phases, the owners, and every field, step by step.

Walk through it →

Everything you need is in the product

No starter tier with the useful parts locked away. One plan, with everything that makes a process work.

Required fields and custom validation

Length, range, dates, file types, allowed values. Cross-field rules for when one answer requires another. The pipe enforces them before a card can move on.

Formula fields

Computed fields that read other fields. Circular references are caught when you save the formula, so a pipe can’t get stuck on itself.

SLA tracking

Time limits per phase and per pipe. Choose a wall-clock, weekdays-only, or business-hours calendar with holidays. Late cards say how late they are.

Automations (coming soon)

Native connectors for Zapier, Make, and n8n are on the way. Because the fields are already filled in by the time a card moves on, an automation will do the right job with the right data. Until they ship, webhooks and the API cover it.

Webhooks

HMAC-signed events for everything that happens to a card. Failed deliveries retry with backoff, so a downstream blip doesn’t cost you the message.

Roles & access

Team roles cascade into pipes; per-pipe admin / member / viewer overrides. Field visibility and editability are role-aware.

Migrate in

Bring pipes across with the Pipefy importer. Imports run in the background so a large migration never blocks your team.

A generous API

Full read and write access, with thousands of API calls per editor included every month. Enough headroom for AI agents, not just dashboards — build your own tooling on top of your own data.

Full feature list: see what Track40 does.

Start running your work through Track40

30 days free, no card required. After that, one plan with everything included: US$12 per editor per month. Your data stays put.

Start free trial See pricing