Bonsai bundles a lot into one subscription: proposals, contracts, time tracking, invoicing, even basic project and task management and a client portal. For freelancers who want a single tool covering the business side end to end, that consolidation is genuinely appealing. The question worth asking before assuming it covers everything is narrower than "does Bonsai have project management?" It's what a client-facing approval process needs, and whether the records Bonsai keeps would settle a disagreement about it.
A disclosure first. We make SwiftSignoff, which is built for that approval layer, so we have an interest in this comparison. We've tried to stick to what Bonsai's own pages and help articles say, and to flag what we couldn't confirm. That turned out to matter, because Bonsai's documentation is more capable than a quick read of its reputation suggests.
What Bonsai's project features actually cover
Bonsai's pricing page (https://www.hellobonsai.com/pricing) shows a per-user price ladder. At the time of our check, annual billing came to $9, $19, $29 and $49 a month for Basic, Essentials, Premium and Elite, with monthly billing at $15, $25, $39 and $59 (the page is undated, so confirm before you decide). Basic covers time tracking, task management and unlimited projects. The client portal arrives with Essentials, and the page lists client tasks and messaging under Premium. There's a 7-day free trial.
The portal is more client-facing than "internal tracking" implies. Bonsai's client portal page (https://hellobonsai.com/client-portal) says clients can "view real-time project progress, milestones, and deliverables," see assigned tasks, "provide feedback directly on deliverables," exchange messages, and reach shared files, invoices and payments. Its help article (https://help.hellobonsai.com/en/articles/4409019-how-to-use-the-client-portal) adds that clients can upload files, collaborate on tasks if you enable that, and reply to project messages from the portal or by email. And on friction: Bonsai's page says clients can open the portal through secure links "without requiring them to create an account."
That last point matters for how we compare. Login friction isn't a difference between Bonsai and a dedicated tool. Bonsai's own pages describe link-based access too. If a difference exists, it has to live in what happens at the approval step.
Where the gap shows up
Here is what we found, and what we didn't. None of it is a claim that Bonsai can't do these things, only that we found no documentation of them.
A formal approval action
The portal page says clients can give feedback on deliverables. We couldn't find a description of a sign-off action: a client approving a specific deliverable, with that decision recorded. Neither the portal page nor the help article mentions approvals, and a competing vendor's review of Bonsai (https://assembly.com/blog/hello-bonsai-review) also doesn't cover them. Feedback and approval are different things. Feedback says "change this." Approval says "this is accepted," and it's the second one you'd want to point to in a dispute.
Version comparison
We found no documentation of showing a client what changed between draft 1 and draft 2. Files can be shared and uploaded, but nothing we read describes comparing versions.
Revision limits
Bonsai can track time against a project, which is a real strength. We found no concept of "2 rounds of revisions included" as a rule the client sees and bumps up against.
What a "done" task means
The help article describes clients seeing shared tasks and progress. It doesn't say clients can mark tasks complete or that a task's status represents their sign-off. Without that, a "done" label is a status, not a decision. We'd confirm this one with Bonsai's support, since the documentation is silent.
Why time tracking doesn't close the loop
Time tracking feels like the answer to scope creep: log the hours, see the overrun, act. It helps, but it's a record of cost, not a control on scope, and the research on why explains where it falls short.
In 1994, Roger Buehler, Dale Griffin and Michael Ross published a set of studies on what they called the planning fallacy, in the Journal of Personality and Social Psychology (paper: https://bear.warrington.ufl.edu/brenner/mar7588/Papers/buehler-et-al-1994.pdf). In one study, honors students predicted their thesis would take an average of 33.9 days and took 55.5. Only about 30% finished by the date they'd called their best estimate. In a later study, only about 29% of students in the control group finished their projects by their predicted date.
Two findings carry over to freelancing:
- The error comes from how we forecast. When participants thought aloud, about 74% of their thoughts were about future plans and only about 7% about past experiences. We build a story of how the job will go and neglect how similar jobs have gone. Observers predicting someone else's tasks were pessimistic and tended to use the person's track record.
- Remembering isn't enough; linking is. In the intervention study, participants who only recalled past experiences did only a little better (38.1% on time). Participants who recalled past experiences and explicitly linked them to the current task did much better: predictions averaged 7.0 days against 7.0 actual, with 60% finishing on time.
Apply that to a revision estimate. When you scope a fixed fee, you're the "actor" building a hopeful plan. Your time log is exactly the past experience the study says we neglect. The log doesn't fix the problem by existing. Reading it back before you quote, and asking what it says about this client, is the linking step.
But look at what time tracking can't do. It tells you, at the moment you look, that you've spent more hours than planned. It doesn't show the client "round 3 of 2," and it doesn't create a dated record that they approved a version before the next round began. That is the gap the original question was circling: the log serves your estimates, and a client-facing approval layer serves the disagreement.
What the client-facing side needs is a cap they can see and a record of every decision made against it:
SwiftSignoff featureRevision limits plus a permanent, timestamped decision log
A caution on the research: the participants were students working on academic and personal tasks, not freelancers on client work. The authors also note that the interventions reduced optimism without making predictions reliably accurate; they shifted the mix of over- and underestimates. And they argue the optimism may be functional in some cases, since it may boost motivation, even though it's costly when the underestimates are severe. So treat this as an explanation of why overruns are normal, not as a promise that any habit will eliminate them.
A worked example
The figures below are illustrative.
Amara is a freelance brand designer on a $3,000 fixed fee for a logo and brand guide. She wants to earn $100 an hour on it, which means 30 hours of work. She budgets 8 hours for revisions: two rounds at about four hours each, as her contract states.
The client sends feedback by email, then through comments in the shared file, then on a call. By delivery she has done four rounds. Her time tracker, which she kept faithfully, shows revisions averaged 4.75 hours, 19 hours in all. That's 11 hours over budget. At her $100 target rate, that's $1,100, or about 37% of the fee.
Bonsai's time tracking showed her all of this. What it didn't give her is what she needed in week three: a point where the client saw "this is round 3 of 2 included" and chose to continue under a change order. Her hours log recorded the cost. Nothing recorded the client's agreement to each round.
Her estimate was also classic planning-fallacy territory. She had finished three similar projects in the past year and her logs showed revision time running well above plan on each, but she quoted the new one from the story, "this client seems easy," not from the log. Reading her last three projects' revision hours before quoting would have been the linking step.
Where the two tools complement each other
Bonsai's invoicing and time tracking are strong enough that most freelancers using it for those purposes don't need to replace them. The gap is in the client-facing review layer, which is the piece SwiftSignoff is built around: a zero-login portal for the actual deliverable review, with revision limits, a real diff/deck/video review module depending on the asset type, and a permanent decision log, running alongside Bonsai's invoicing rather than replacing it.
An honest note on when you shouldn't bother. If your deliverables are few and simple, your clients give clear feedback in one place, and Bonsai's portal feedback and messaging thread already hold your approvals, an extra tool is overhead. Bonsai's portal keeps all project messages in a single thread, which may be enough for straightforward work. The case for a dedicated layer strengthens with revision-heavy work, multiple stakeholders, and any history of disputes.
If the admin-side tool you're weighing is Dubsado rather than Bonsai, we looked at the same question there:
Related comparisonDubsado Alternative for Solo Consultants Who Need Real Client Approvals
Test it yourself in ten minutes
Bonsai offers a 7-day trial, and the fastest way to settle the question is to run it against the standard you care about. Put a live project in, invite yourself as a client through the portal preview and, ideally, a second email address, then ask:
- 1Can the client open a specific version of a deliverable and tell it apart from the previous version?
- 2Can they approve it, and does the product record who approved what and when?
- 3Does anything count revision rounds or show the client a limit?
- 4Can you export the record if you need to show it to someone later?
- 5After a month of messages, can you find the one where a decision was made?
Note that Bonsai's preview mode shows you the client's view but, according to the help article, doesn't let you send messages or complete actions, so use a real second email address for the actions. Apply the same five questions to any tool, ours included.
What we couldn't verify
- Absence of documentation isn't proof of absence. Where we say we found no documentation, that's what we mean. Bonsai may do some of these things in ways we couldn't see. Confirm with Bonsai's support or the trial.
- We read documentation, we didn't test Bonsai. The portal page is marketing copy, and what "feedback on deliverables" records and how it displays is unknown to us.
- Plan mapping is unclear. The pricing page lists client tasks and messaging under Premium, and the help article doesn't state plan limits.
- Competitor sources are interested. Assembly's review is from a vendor that promotes its own alternative. We used it for the absence of approvals discussion, nothing else.
- The planning-fallacy research is about students and doesn't prove any particular fix works for freelancers.
Sources
- Bonsai: Pricing (https://www.hellobonsai.com/pricing) — undated; reviewed October 2026.
- Bonsai: Client portal (https://hellobonsai.com/client-portal) and help article How to use the client portal (https://help.hellobonsai.com/en/articles/4409019-how-to-use-the-client-portal).
- Buehler, R., Griffin, D. & Ross, M. (1994), "Exploring the 'Planning Fallacy': Why People Underestimate Their Task Completion Times," Journal of Personality and Social Psychology, 67(3), 366-381. Paper: https://bear.warrington.ufl.edu/brenner/mar7588/Papers/buehler-et-al-1994.pdf
- Assembly, Hello Bonsai review (https://assembly.com/blog/hello-bonsai-review) — competing vendor.
FAQ
Can Bonsai's client portal be customized to function like an approval flow?
Bonsai's portal lets clients view project progress and shared files, upload files, message you, and, according to Bonsai's marketing page, give feedback on deliverables. We found no documentation of a formal approval action, version comparison or revision cap, so building a revision-tracked, logged approval process on top of it would likely require manual workarounds. Check by testing it in the free trial.
Does Bonsai's time tracking help with scope creep?
Indirectly. Tracking hours against a project can reveal that a project is running over, and reading your past logs before you quote helps counter the planning fallacy. But it doesn't prevent the creep itself, since we found no client-visible revision cap tied to it.
Is there a reason to use both tools together rather than one all-in-one alternative?
It depends on your work. For simple projects with clear feedback, one tool is simpler. For revision-heavy work, multiple stakeholders or a history of disputes, a dedicated approval layer alongside Bonsai's invoicing and time tracking can be worth the extra tool.
Does Bonsai's client portal require clients to create an account?
According to Bonsai's own pages, no. Its portal page says clients can use secure links to reach the portal without creating an account, and its help article describes access through a secure email link.
Bonsai keeps your business running. A dedicated portal keeps your scope protected.
SwiftSignoff is not affiliated with, sponsored by, or endorsed by Bonsai. Bonsai is a trademark of its respective owner.