A practice does not lose money on the technical work. It loses money on chasing the same bank statement four times, on a deadline that lived in one manager's spreadsheet, and on work that got done in March and billed in June or not at all. NOWORX handles that surrounding layer — the per-client deadline map, document collection, who is on what, and the fee that follows. It does not prepare, calculate or file anything, and it does not replace your accounting or tax software.
Three hundred clients on different year ends, different cycles and different obligations, held together by a spreadsheet with conditional formatting that one manager maintains. Everyone else works from a copy that was accurate last Thursday. When that manager takes two weeks off in a busy period, the practice discovers exactly how much of its risk management was a single file.
The technical work takes hours. Getting the bank statements, the invoices, the mileage log and the one missing signature takes weeks, in five separate email threads per client, repeated every cycle. It is the largest consumer of junior time in most practices and the least visible line in any report.
Jobs are handed out client by client, by whoever happened to be free that morning, and the real distribution of work is invisible until someone in the middle of a busy period stops coping. The partners were not careless — there was simply no view that put every open job, its stage and its owner in the same place.
An extra query, a rebuilt set of records, a call that turned into three hours of remedial bookkeeping. It was real work, it was outside the engagement, and it was never written down while it was happening. At billing time the choice is between an awkward conversation and writing it off, and most practices write it off.
Which client always sends the wrong file, whose director takes three weeks to sign, which entity has a peculiar arrangement agreed with the previous adviser. It is never written down because it never felt like documentation — it felt like knowing the client. The successor learns it by making the same mistakes again.
Tap an app name in any step to see what it does.
Every client is one record: entities, contacts, responsible manager, and the engagement scope in writing. Fee proposals and scope are prepared from that record, and the signed engagement documents sit in the vault with their dates, so a renewal or a scope change is visible rather than remembered. Onboarding becomes a repeatable list instead of a habit each manager performs differently.
Obligations and internal cut-offs are held per client on a shared calendar, so the whole practice sees the same picture instead of copies of one person's file. The dates come from you — imported from the schedule you already maintain or entered per client. We do not assert filing dates on your behalf, because those depend on jurisdiction, entity type and facts we are not in a position to judge. What the system contributes is that once a date exists, it is visible, owned and warned about.
Each client gets a request as a structured checklist rather than a paragraph in an email, so what is outstanding is a state rather than a matter of interpretation. The department agent follows up on the items still missing, escalates to the responsible manager when the window is closing, and stops asking for what has arrived. Incomplete records surface as a flag while there is still time to do something about it, not in the final week.
Open jobs, their stage and their owner sit on one board, so the partner conversation about capacity happens against a picture instead of an impression. Effort recorded against the job makes the difference between a client that looks profitable and one that is. Recurring notes about a client's quirks attach to the client record, which is how a handover stops being a re-learning exercise.
Out-of-scope work is captured when it happens, against the client and the job, so it survives to billing instead of being remembered as goodwill. Invoicing and fee documents are raised from the same records the work sat on. Practice-level views — recovery by client, work in progress by manager, which engagements consistently run over scope — come from the data the team already filed rather than from a quarterly spreadsheet exercise.
No, categorically. It does not prepare accounts, does not calculate tax, does not produce filings and does not submit anything to any authority anywhere. It also does not replace your accounting, bookkeeping or tax software. It manages the practice around that work: deadlines, document collection, assignments, engagement records and billing. If a system ever tells you it can do the technical work, that is a different and much larger claim than the one we are making.
From you. Dates are entered or imported per client, and the practice owns them. We deliberately do not ship a set of filing dates and assert they apply to your clients, because obligations depend on jurisdiction, entity type, elections and facts that a software vendor has no business assuming. Once your dates are in, ownership, visibility and escalation are handled for you.
Access is scoped by department, team and role, so staff see the clients they are engaged on rather than the whole book. Where a client relationship requires stricter separation, that separation is configurable rather than a matter of trust. You also decide what enters the workspace in the first place — including keeping working papers in your existing systems and using only the workflow layer here.
Only what you put into the workspace, and only within the access scope you set for that department. Many practices run this as a workflow layer — deadlines, checklists, assignments, billing — and keep the underlying records in their accounting software. That is a legitimate configuration, not a degraded one, and it is the one we would suggest starting with.
It sits beside it, not on top of it. The parts that are not in the tax software — who is chasing which document, which client is three days from a cut-off, what is unbilled — are exactly the parts that currently live in email and one manager's spreadsheet. The agent brings those to people in chat, so for most staff it is a message, not a system to remember to open.
The client roster imports from a spreadsheet, and so does the deadline schedule you already maintain. The realistic first step is one team and one cycle: load their clients, put the deadline map and document chasing in, and see whether the chasing volume drops before rolling it out to the rest of the practice.
No. Review and sign-off stay with the qualified people who are responsible for them, and the approval chain reflects your existing hierarchy rather than imposing one. What changes is that a job waiting on a partner is visible as waiting, and gets chased by an agent rather than by a junior who is uncomfortable chasing a partner.