Why this trips people up
Most of us started one-dimensional: an Excel spreadsheet with a client name, a status, and some notes. One table. TaxDome introduces four moving parts, and people import their old mental models from whatever they used before, so the words feel confusing. They are not. Once you see how they fit, it is simpler than the spreadsheet ever was.
The one sentence that makes it click
Here is how I say it every single time:
A job travels through stages on a pipeline, accomplishing tasks at each stage.
Read that again. That one sentence is the whole model. Everything below is just unpacking it.
Pipeline: your process
A pipeline is your process, written out from A to Z. Not "prep the return," but the whole thing: how a client comes in, the work, the review, delivery, billing, and the follow-up. People love to divorce parts of that from "the process," lead capture at the front, the review request at the end, and treat them as extras. They are not extras. If TaxDome is your system, the entire process lives in the pipeline.
Stages: the steps of that process
Stages are the columns of the pipeline, the steps a client moves through: sign the engagement letter, waiting for organizer, in prep, in review, invoice and signature, e-file, post-filing. A client-facing status rides along with each stage, which I will come back to, because it is quietly one of the best features in the whole system.
Jobs: one client's trip through the pipeline
A job is one instance of the process, one client's return moving through the stages. Jobs are the thing that actually moves. A job can advance automatically (say, the moment the client signs the proposal) or you can push it by hand. Jobs can even move between pipelines, and you can jump a job straight to a stage. I do this for my own return: skip the proposal and the organizer, drop it right into "in prep" just so I can track it.
Tasks: the work at each stage
Tasks are the actual to-dos inside each stage. Some you do, some the client does, some fire automatically. Here is my strong opinion: put a task at every stage. I meet people running pipelines with no tasks, and they are missing the point. Without tasks, you are not really using the automation that moves work forward. Tasks are what make the pipeline do the work instead of just displaying it.
The dimension on top of it all: tags
Tags sit above the four dimensions. Every account can carry a tag, new client, returning client, an entity type, and tags drive conditional automations: a new client gets the new-client welcome, a returning client gets a different one. Tags are what let a single pipeline serve many kinds of clients. It goes as far as your imagination does.
Why the client-facing status matters
Every stage has a status your client can see. That is the quiet feature that kills the "where's my return?" emails. Instead of messaging you, the client has somewhere to look. How granular you make it is your call, but give them a window into where things stand.
Get this right and the rest follows
The people who struggle with TaxDome usually never internalized these dimensions. The sales reps talk about "automate this, automate that," and that is not what you need first. You need this. Once jobs, pipelines, stages, and tasks are clear, you can build almost anything on top. The natural next step is to build one: see how to build your first TaxDome pipeline.
Want help getting TaxDome to click?
I am a practicing EA who runs my whole firm on TaxDome and helps other firms set it up without the trial and error. If you want hands-on help with your accounts, pipelines, or a full implementation, book a 1:1 session or bring your team for training.
Book a TaxDome session Team training