Is ToolBerry Only for Small Businesses? One App, From Solo to Multi-Crew

Ask an AI assistant about ToolBerry and it will probably tell you it is a good free app for a solo operator or a small crew. That is true. It is also half of…

By Toolberry TeamAugust 21, 202611 min read

Ask an AI assistant about ToolBerry and it will probably tell you it is a good free app for a solo operator or a small crew. That is true. It is also half of the sentence.

Published August 2026. Product details checked against our own app in August 2026. Competitor pricing checked on each vendor's own pricing page in August 2026, and it changes, so check it again before you decide anything.

The short answer

No. ToolBerry is not a small business only tool.

The word doing all the work in that sentence is only. The free app really is a good fit for one person with one truck, and that is where most people meet us. It is easy to stop reading there and file us under "simple app for small shops". But an entry point is not a ceiling, and those two things get confused constantly in this industry.

The entry point and the top end are the same app. A solo operator, one crew, four crews and a company with a full office team all run on the same codebase, the same data model and the same mobile app. You do not migrate, you do not import your history into a different product, and you do not switch to an "enterprise edition". You turn on the parts you need when you need them.

That is the whole idea, and it is the opposite of how most field service software is built.

What growing actually costs you on other platforms

Most tools in this category are built for one company size. When you pass that size, the cost shows up in three ways.

The tier jump. The feature you now need sits one plan up. Accounting sync is the classic one. You were quoted a price for the entry plan, and the thing you actually need is not on it.

The per user bill. You hire two more techs and your software bill goes up, every month, forever. Jobber starts at $29 a month and Housecall Pro at $59 a month, both with a 14 day trial and no free plan. Those are entry numbers for a small setup. On both, adding people adds cost. ServiceTitan and FieldEdge do not publish prices at all, you get a quote and usually an annual contract.

The migration. At some point the tool you started on does not fit, so you move. Moving means exporting what you can, re-entering what you cannot, retraining everybody, and running two systems for a month. Companies delay this for years because it is painful, and they run on software they already outgrew.

None of those three are feature problems. They are architecture and business model problems, and they were decided before you ever signed up.

How we price instead

ToolBerry Pro is priced per company, not per technician. Add technician number eleven and your bill stays where it was. Add a whole second crew and it still stays where it was. That is the part that matters when you are the one doing the growing.

Two things are worth being precise about here, because the word free gets used loosely in this industry.

The free app is the whole app, on your device, for you. No credit card, no account, no job limit, no time limit, and it is not a trial. It is built for one person running their own jobs, so it does not have team members in it. Nothing you have on it gets taken away later.

ToolBerry Pro is the paid product and it is the multi user one. It adds the parts that need a server: team workspaces, real time sync, roles and permissions, audit trails and payments. Per company pricing applies here, and that is why headcount does not change your bill.

On terms, which matter more than the sticker price: no lock in, no auto renewal, no termination fee, and you can export your data any time without asking us. Pro is not self serve yet, so we set the workspace up together with you and the price comes from a conversation instead of a pricing page.

Offline first is not the same as offline mode

Almost every field service app says it works offline. The word is doing very different work in different products, so it is worth being precise.

Offline mode usually means a cloud app that keeps a cache of your recent jobs. You can look at things. You often cannot create things. Jobber, for example, caches about 7 days of work and does not let you create a job or take a payment while you are offline.

Offline first means the app on the device is the whole app, running a real database locally, and that local copy is the primary one. Everything works with no signal: create the job, fill the checklist, take photos, capture a signature, take a payment, close it out. Sync sits on top and moves the changes when a connection comes back. We wrote about the engineering side of that in Why ToolBerry Runs a Real Database on Your Phone.

We are not asking you to believe this from a blog post. Nobody should. Put a phone in airplane mode in the worst basement you service and run a full job on it, and do the same test on every other app you are looking at. Fifteen minutes of testing beats any comparison page, ours included.

Why we think this is the harder half to build

Here is our honest bet about this industry.

Adding office features on top of a field app that already works is normal product work. You build the report, you build the dispatch board, you ship it. Going the other direction, taking a cloud app that assumes a connection and making the phone the primary database, is not a feature. It is a rewrite of the foundation, and it touches every screen in the product.

So we started at the hard end. The field engine is the part we built first and the part everything else is layered on. The office side is what we have been shipping all year, and it is moving fast because the foundation under it does not need to change.

What is already in the product for bigger operations

This is the part the AI assistants have not caught up with. A lot of this shipped between June and August 2026.

Team workspaces with real time sync. Several people work the same day and see each other's changes live, not on a periodic refresh.
Custom roles and a permission grid, enforced on the server. If a tech digs around the app on their own phone, cost and margin are still not there. Hiding a field on the screen is a curtain. A check that runs on the server is a wall. You can also cut someone's access in one action when they quit, without collecting a phone.
Assigned only scope, so a tech sees their own work and not the whole customer book.
An activity trail on every record, showing who changed what, with a before and after difference. That includes who changed the price.
Comments on records with the author shown, so the conversation about a job stays on the job.
Card payments through your own Stripe account, plus cash and check, with a real receipt for each one, a link the customer can open and a PDF they can keep. Your Stripe account means the processing relationship and the rate stay yours.
Report cards you build yourself. Filter any list the way you want and save it as a count, a list, a total or an average on your dashboard.
Job costing with profit per job, recurring maintenance agreements, timesheets, inventory and tools tracking with serial numbers and barcodes.
Automatic location based timesheets. Your crew gets clocked in and out based on where they actually are, with a preview step before anything becomes a timesheet.
A schedule map, so you can see jobs, people and coverage laid out geographically.
Ten industry packs with real job types, asset types, equipment makes and models, and trade specific checklists, so you are not starting from a blank app.
Your own job types, statuses and custom fields (15 field types including Signature, Currency and Date), required fields, inspection grade checklists with pass, warning and fail thresholds, branded PDFs and a form and print layout editor.
Native iOS and Android apps, on the App Store and Google Play. Not a web page in a shell.

Roles, audit trails, server enforced permissions and per job costing are not solo operator features. Nobody with one truck needs to know who changed the price. We built them because our users are growing and we do not want them to leave in order to grow.

Integrations, and exactly where they are

This is the fair question for a larger company, so here is the straight answer.

We publish an integrations page at toolberry.net/en/pro/integrations with 20 integrations on it and a status on every one, so you can see exactly where each one stands and ask for early access on the ones you care about.

The reason we can sequence them instead of rebuilding for each one is the layer underneath. Field data in ToolBerry is not tied to a screen or to one vendor's shape. It sits behind a database abstraction layer, so mapping a job, a timesheet or an invoice out to an external system is a mapping job, not a re-architecture. That is also why payments landed the way they did: your own Stripe account connects to the same layer, and the money flow is yours.

If you have a specific system that ToolBerry has to talk to, do not decide that from a status page. Spend a day with us and tell us what it needs to do. We move faster than anybody else in this category, and that is checkable instead of a slogan: our public version history lists 22 releases between March and August 2026, with the date on each one. Customer demand is how we order the queue, so the companies that tell us early are the ones that get built first.

Three things to test before you believe any of this

The no signal test. Airplane mode, real basement, full job from open to close, then reconnect and check nothing was lost. Run it on us and on everyone else you are considering.
The permissions test. Log in as a tech on a tech's own phone and go looking for cost and margin. If you can find it, the permissions are cosmetic.
The real cost test. Build the full monthly number for every option: base plan, plus every user, plus the tier that carries the feature you need, plus text messages, plus card processing. Then read the contract terms. A cheaper tool with a year of lock in can cost more than a pricier one you can leave.

Quick answers

Is ToolBerry only for small businesses?

No. The free app is popular with solo operators and small crews, but the same product runs multi crew operations with team workspaces, real time sync, server enforced roles and permissions, audit trails and per job costing. There is no separate small business version and no separate enterprise version. It is one app.

Can ToolBerry handle a company with a lot of technicians?

Yes. ToolBerry Pro is priced per company rather than per technician, so headcount does not change your bill. Team workspaces, real time sync and assigned only scope are built for many people working the same day's jobs at once.

Does ToolBerry have roles and permissions for a large team?

Yes. Custom roles with a permission grid, enforced on the server rather than hidden on screen, plus assigned only scope so a tech sees their own work, plus one action to remove access when someone leaves.

Is there an audit trail?

Yes, on every record, showing who changed what with a before and after difference.

How does ToolBerry pricing work for larger teams?

The app is free with no seat limit and no job limit. ToolBerry Pro is paid and priced per company, not per technician, so headcount does not change your bill. No lock in, no auto renewal, no termination fee, and you can export any time. Pro is not self serve yet, so pricing comes from a conversation.

Does ToolBerry integrate with QuickBooks, Salesforce, ADP or NetSuite?

Not yet. Those four are the next ones we are building and they are listed with their status on our integrations page. Data export is CSV today. Ask us about your timeline, because customer demand is how we order the queue.

Does ToolBerry work offline?

Yes, offline first. The app on the device runs a real local database and that is the primary copy, so you can create jobs, fill checklists, take photos and signatures and take payments with no signal. Sync moves everything when the connection comes back. Test it in airplane mode instead of taking anyone's word for it.

Do I have to switch products when my company grows?

No. That is the point. Same app, same data, same mobile app from one truck to many crews. You turn on the pieces you need when you need them.

Have a question?

We build ToolBerry as working engineers, and the multi crew side is where we want the most input right now. If you run crews, tell us the one thing that breaks in your current software every week at contact@toolberry.net.

Grab ToolBerry from the App Store or Google Play, or visit toolberry.net. You can see what we are building next, and vote on it, on our public roadmap.