If you run a landscaping business out of a Ford F-150 in North County San Diego, you already know the truth that no glossy SaaS website wants to admit: most "field service software" wasn't really built for you. It was built for the people who buy software - office managers in headsets, dispatchers behind two monitors, owners of regional chains with payroll departments. Not for the guy who wakes up at 5 a.m., loads a trailer in the dark, runs eleven properties before lunch, and writes the day's invoices on the back of a Home Depot receipt at a stoplight.

That's who ToolBerry is for. And it's free.

This article is a long one because the problem is a long one. We'll walk through it the way a landscaper would actually live it - through the eyes of a composite character we'll call Carlos in Escondido, through a chaotic Tuesday compared to a calmer one a few months later, and through our own perspective as the team building ToolBerry. We kept meeting small operators getting pushed around by tools that were supposed to help them, and we got tired of it.

Meet Carlos - the solo operator who holds everything in his head

Carlos has been mowing lawns in Escondido, San Marcos, and parts of Vista for nine years. He started with a push mower in his cousin's truck and now runs a two-man crew with a 16-foot trailer, two riders, blowers, edgers, a hedge trimmer that he keeps having to repair, and one Stihl chainsaw he doesn't let anyone else touch.

On a normal week he services around fifty residential properties. Most are weekly mow-and-blow, some are biweekly, two are monthly maintenance contracts, and a rotating handful are one-off cleanups. He does spring cleanups in March, irrigation tune-ups in April, and fall cleanups in November. He installs about a dozen small landscape jobs a year - a DG path here, a few yards of mulch there, a couple of palms.

If you ask Carlos how many customers he has, he'll squint and say "around fifty… maybe sixty?" If you ask how much each one pays, he'll tell you exactly to the dollar. If you ask which gate codes go with which house, he'll start scrolling through three years of text messages with his wife Maria, who books most of the new work from her phone.

Carlos's business runs on three things: a beat-up clipboard, a contacts list with 287 entries (most labeled "Rancho Bernardo blue gate" or "Mrs. K trash day"), and his memory. The memory is the most important one. And it is also the biggest problem.

When everything important about your business lives in one person's head, the business can't get bigger than that head — and it can't take a day off.

This is what people mean when they say a small business "doesn't scale." It's not a strategy problem. It's that Carlos is the system. If he gets the flu, fifty yards don't get mowed. If he forgets that the Hendersons asked for an extra hedge trim this week, he loses a customer. If his crew shows up at the wrong gate because he forgot to forward the new code, that's twenty minutes of lost time and an annoyed homeowner.

This is the reality for the vast majority of landscapers in Southern California. There are roughly 642,000 landscaping businesses in the United States and about 1.3 million people working in the industry, with California consistently ranking in the top three states for both businesses and workers. The average landscaping company has only about 19 employees, but in San Diego the median is far smaller - a one-truck, one-trailer, two-person operation is the norm, not the exception.

And more than 80% of the landscape workforce is Latino by some industry estimates, while only about 6% of owners and executives are identified as Hispanic. There's a language story tucked into that gap. We'll come back to it.

A Tuesday in Carlos's life - before ToolBerry

Let's walk through one day.

5:42 a.m. - the day starts on a notepad

Carlos is on his second coffee, scribbling the day's route on a yellow legal pad. He's trying to remember whether the Olsons in Carmel Mountain wanted weekly or biweekly. He thinks weekly. He thinks. He texts Maria: "Did Olson change to weekly?" She's still asleep.

7:15 a.m. - gate code roulette

The crew shows up at a gated community in Rancho Santa Fe. The code Carlos has on his phone is from 2024. They wait fifteen minutes for the property manager to call back. The gardener at the next house over lets them tailgate in.

9:50 a.m. - a customer calls with a question

Mrs. Patel calls. "Did you guys pull the dead lavender like we talked about in February?" Carlos has no idea. He didn't write it down. He says yes anyway and hopes for the best.

11:30 a.m. - lunch and invoicing

Carlos eats a burrito in the truck while filling out three invoices on an invoice book from Office Depot. He'll stick stamps on them tonight. Two of them have the wrong amounts written on them - one too high, one too low. He'll never notice.

2:15 p.m. - a lead slips away

A homeowner in Poway texts asking for a quote on a backyard cleanup. Carlos says he'll get back to her tonight. He won't. He'll forget. She'll hire the next guy who answers within two hours, because she's 31 years old and that's how she lives.

6:50 p.m. - trying to remember who paid

Back home, Carlos opens his Wells Fargo app, his Venmo, his Zelle, and the Cash App he set up for one customer who insisted. He's trying to figure out who paid for September. Three customers are behind. He thinks. Maybe four.

9:40 p.m. - one more hour of paperwork

Maria types out the next month's recurring schedule into a Google Sheet that only she understands. Carlos falls asleep on the couch. The legal pad is on the floor.

This is not a man who is failing. This is a man who is exhausted by the administrative part of running a business he is otherwise excellent at. And every single one of the friction points above - gate codes, recurring schedules, invoicing, follow-ups, who-paid-what - is a software problem that has been "solved" by half a dozen big platforms.

It's just that none of those platforms were really built for Carlos.

Why the existing apps don't reach the Carloses of the world

Let's be direct, because Carlos would be.

Jobber, Housecall Pro, and ServiceTitan are three of the dominant field service management platforms in the country. They are good products. They genuinely help certain types of businesses. But they were not designed for a one-truck shop that doesn't trust SaaS, doesn't speak fluent English in the office, and doesn't have $300 a month to spend before they earn their first invoice of the day.

Here's what they actually cost, based on published pricing pages and aggregated user reports as of early 2026:

• Jobber: Starts at $39/month for one user (Core plan, billed annually). Adding users runs about $29/month each. With necessary add-ons like the AI Receptionist ($99/mo) and Marketing Suite ($79/mo), real-world cost for a small team is $200–$400/month, plus 2.9% + $0.30 per card transaction on Jobber Payments. A business invoicing $30K/month can pay roughly $900/month in card-processing fees alone.
• Housecall Pro: Starts at $59/month (Basic, 1 user). The jump to Essentials runs to $149/month, and MAX pricing isn't published - you have to call. Multiple review sites note that "add-on cost creep" is the most common complaint. Realistic small-team cost: $200+/month before processing fees.
• ServiceTitan: Roughly $250–$500 per technician per month, not published publicly. Implementation fees range from $5,000 to $50,000+. One reported 20-tech company spent about $145,000 in their first year. Multi-week implementation. Annual enterprise contract.

Then there's the part the pricing pages don't show.

Every one of these platforms requires you to sign up, create an account, hand over your email, and often sit through a sales call or onboarding flow before you can do anything. They store your customer data on their servers. They charge for export. They lock features behind tiers. They assume you have Wi-Fi. They assume you read English. They assume you have a desk somewhere.

For someone like Carlos - who has been told for fifteen years that "the cloud" is where his business goes to disappear, who has watched a buddy get locked into a $400/month contract he couldn't get out of, who literally works on a property in Fairbanks Ranch where the LTE signal cuts out behind the hedge - that's a wall of friction tall enough to turn around at.

The big platforms split their product into a mobile app for the field and a web console for the office: two UIs, two mental models, two things to teach your crew.

There's a real gap in our industry, and it's worth naming honestly. Companies like BrightView, LandCare, and TruGreen - the regional and national giants - run on enterprise systems with route optimization, GPS fleet tracking, automated CRM, integrated payroll, and AI-driven scheduling. The small operator down the street, doing arguably better work for half the price, runs on a clipboard, a phone, and a memory.

And here's the thing: the clipboard system has built thousands of great businesses. Honestly. There's nothing wrong with the way Carlos has always done things. The problem isn't pen and paper. The problem is that the on-ramp to adding a tool - for the day he decides he wants one - was built so steep that anyone who tried to step on it got priced out, locked in, or buried in a 30-minute signup flow.

Why ToolBerry exists in the first place

ToolBerry got built because the same conversation kept happening. Solo operators and two-person crews who were excellent at the actual work and slowly drowning in the admin around it — not because they lacked discipline, but because every "solution" they'd tried demanded a credit card, an email address, and a Wi-Fi signal before it would even introduce itself. After enough of those conversations, building something different stopped being optional.

Most FSM tools fail small service businesses in three ways:

1. They cost too much for solo operators and small crews.
2. They require lengthy onboarding and account setup before they deliver any value.
3. They don't work without reliable internet - which is exactly where field workers spend their day.

So ToolBerry was designed from a different starting point: what would a tool look like if it had to earn its place in the truck, with no signup form and no Wi-Fi?

The answer turned out to have a few uncomfortable consequences for the rest of the industry. If you built the app offline-first, you didn't need a backend server for solo users. If you didn't need a backend, you didn't need accounts. If you didn't need accounts, you didn't need a signup wall. And if you didn't need any of that, you could give it away - really away, free forever, not "free trial," not "free for 14 days," not "free until we ask for your credit card."

Under the hood, the free tier of ToolBerry runs entirely on your device using a real on-device SQLite database - the same engine that powers a huge slice of the world's mobile apps. It's not a localStorage hack. It survives browser cleanups, supports gigabytes of data, handles real queries with joins and indexes, and tested clean with 100,000+ records. Backup is via your own Dropbox if you want it. Your customer list lives in your pocket, not on someone else's server.

That's the architectural commitment. The cultural commitment is more important: ToolBerry is built bilingual, English and Spanish, from day one - not bolted on later. For a SoCal landscaping crew, where the owner often speaks Spanish at home and English with customers, that's not a feature, it's a deal-breaker the other apps haven't solved.

If your customer list is on someone else's server, your business belongs to a vendor. We'd rather you keep it.

The same Tuesday, a few months later - after ToolBerry

Now let's run that same day again. Carlos has been using ToolBerry for about ten weeks. Here's the difference.

5:42 a.m. - the schedule is already there

Carlos opens ToolBerry on his phone before he gets out of bed. Today's route is queued up - the Olsons (weekly), the Hendersons (biweekly + extra hedge trim - flagged in the notes from last call), the Patels, eight more. He doesn't have to remember anything. The app already remembers.

7:15 a.m. - the gate code is in the property notes

The Rancho Santa Fe gate code is right there on the customer's site record, along with a one-line note: "Park in the second driveway, dog is friendly, irrigation valve box is behind the bougainvillea." The crew is in and working in three minutes.

9:50 a.m. - the lavender question has an answer

Mrs. Patel calls. Carlos taps her name. The work order from February shows the dead lavender was pulled, with a before-and-after photo. He sends her the photo by text without leaving the app. She thanks him. She tells her sister in Encinitas about him.

11:30 a.m. - invoicing happens at the job, not at midnight

Carlos finishes a one-off backyard cleanup. He marks the job complete in ToolBerry. The invoice generates with the right line items because he set up the recurring service template once, weeks ago. He sends it to her with a tap and is back on the road before the trailer's loaded.

2:15 p.m. - the Poway lead becomes a job

The Poway homeowner texts at 2:15. By 2:23, Carlos has created her customer record, put a quote together using a saved template, and texted it to her with three line-item options. She approves it from her phone. He didn't pull over. He didn't open a laptop. He didn't even leave the truck.

6:50 p.m. - who paid is a tap away

The “Open invoices” view shows the four customers behind on payment, sorted by how late. Carlos sends two friendly reminder texts. Two reply within the hour.

9:40 p.m. - Carlos goes to bed

Maria isn't typing into a Google Sheet. The recurring schedules are already set. She's watching a movie.

This isn't a fantasy. It's what happens when the information that used to live in someone's head finally lives somewhere that won't forget. Same person, same crew, same trucks. Just less drag.

Here's a useful question to sit with: if you had to miss next Friday and someone else had to run your route, could they? Not could they do the work — could they find the gate codes, the customer notes, the schedule, the open invoices? If the honest answer is no, that's not a sign you're failing. It's just the moment the clipboard has done what it can do for you, and a tool somewhere in the day would help.

The specific landscaping problems ToolBerry solves

We could write a feature list, but we'd rather walk through the actual landscaping pain points and show how the tool maps to them.

Recurring service scheduling - weekly and biweekly mowing

The bread and butter of any landscape maintenance route. Set the cadence once per customer, and the schedule rolls forward. No re-typing into a sheet every Sunday night.

Customer, site, and contact records - with the stuff that actually matters

Every customer has a record. Every customer can have multiple sites - think HOAs, property managers, snowbirds with two houses. Every site has its own notes: the gate code, the dog warning, the irrigation valve location, the trash day, the "don't blow leaves toward the koi pond." These are the details that separate a professional crew from a guy with a mower.

Work orders with photos and notes

Job-by-job documentation. Before-and-after photos for spring cleanups. A note that says "replaced one zone-3 sprinkler head - charged customer $18 for parts." When Mrs. Patel calls eight months later, you have an answer in three taps.

Recurring + one-off jobs in the same view

Most landscapers blend weekly maintenance with seasonal work - spring cleanups, fall cleanups, irrigation winterization, mulch installs, palm trimming. ToolBerry's work-order workflow handles both: Draft → Pending → Scheduled → In Progress → Complete, with audit history at each step.

Asset tracking for equipment and customer property

Track equipment service intervals on the company side, and on the customer side track things like irrigation systems, outdoor lighting controllers, and pumps. Asset records support parent-child relationships - a controller has zones; a zone has heads - so when something breaks, the history is right there.

Reminders, reporting, and deliverables

Reminders for upcoming jobs and overdue follow-ups. Basic reporting for the office user - not a 33-report enterprise dashboard, but the numbers a small owner actually checks. Deliverables - proposals, service reports, invoices - generated from your job and customer data instead of being typed up in Word at 10 p.m.

Cross-device, cross-platform

One app, every device. iPhone, Android, tablet, laptop, desktop - same screens, same data, same muscle memory. Live on the App Store and Google Play, and as a web app for desk days.

Offline-first, always

This is the differentiator that matters most for landscapers. The basement, the back forty, the gated community where LTE drops, the new build site where the cell tower is half a mile away - they all look the same to ToolBerry. The app doesn't spin a loader. It doesn't lose your photos. When you get back online, changes sync up.

If a tool only works when the Wi-Fi works, it's not a tool. It's a customer of yours.

What's actually changing isn't your shop - it's your customer

Plenty of articles like this love to draw a tidy progression: pen and paper, then a website, then apps, then automation, then AI. As if the goal is to climb the ladder. We don't really believe that. Some of the best landscaping crews we know run almost entirely off a clipboard, and they run beautifully. Pen and paper is a real, working system, and for many small operations it's exactly enough.

What's shifting isn't the right way to run your shop. What's shifting is who's hiring you.

Industry research shows that 66% of millennials prefer an "Uber-like" experience when hiring a service, and 53% of millennials prefer to communicate with service providers over SMS text. Other studies show roughly 91% of Gen Z consumers are adopting digital-first payments, and 38% of Gen Z and millennial customers will give up on a service issue if it can't be resolved through self-service channels.

Translation: the homeowner who buys her first house in San Marcos in 2026 - the one with the new lawn, the dog, and the dream of a desert garden - has been trained by Uber, DoorDash, and Amazon to text rather than call, expect a digital quote, and pay from her phone. She isn't judging your craft. She's judging how easy you are to hire.

The crews who can offer that kind of handoff aren't necessarily better landscapers. They just have a slightly different toolkit on the admin side. The bigger operators feel the difference too - BrightView and TruGreen run on enterprise software stacks, and their dispatchers are piloting AI-assisted routing. None of that makes them better in your customer's yard. It just makes them easier to text from her couch.

ToolBerry isn't asking you to climb a ladder. It's offering one tool you can pick up - when you want to, in the parts of your day where it helps - and leave the rest of your routine alone. Keep the clipboard. Keep the way you greet your regulars. Add a digital quote the next time a younger customer texts. That's the whole pitch.

The cultural layer - why bilingual matters in SoCal

You can't talk about this market and skip language. The U.S. landscaping industry has roughly 500,000+ Hispanic-American workers, and Spanish is by far the most common second language among landscapers - about 77.7% of those who speak a foreign language. In Southern California, that share is even higher.

Yet most FSM software still treats Spanish as an afterthought - a translated FAQ page, a half-localized mobile app. The reality on a North County jobsite is that the owner takes calls in English, dispatches the crew in Spanish, and texts the customer in whichever language they prefer. A tool that flips between English and Spanish cleanly - like ToolBerry does, on every screen, from day one - is a tool the crew will actually use. The other ones get downloaded, opened twice, and never opened again.

That's the part of "adoption" that doesn't show up on a feature comparison chart. But it's where most software dies in this industry.

What a free, offline-first, no-signup tool actually unlocks

Let's zoom out from features for a second and talk about what changes in Carlos's life - and your life, if you're him - once the friction comes down.

• You stop being the only system. When some of what's in your head also lives somewhere that won't forget, the business can grow past you - if you want it to. You can hire a second crew. You can take a Saturday off. You can get the flu without losing fifty yards.
• You stop losing leads in the gap. A 15-minute response window beats a 12-hour one every single time. The Poway homeowner becomes a customer instead of a missed text.
• You stop bleeding on Saturdays. Invoicing in the truck saves you the entire Saturday-morning paperwork ritual that eats half your weekend.
• You can meet your younger customers where they live. They want texts, photos, and digital invoices. You can offer that without paying $300/month for the privilege.
• You stop being one phone-drop away from data loss. Local-first storage with Dropbox backup means your business survives a dropped phone, a stolen truck, a cracked screen, or a bad LTE day.

The free tier is genuinely free. The paid tiers exist for the day your team grows past a couple of crews and you actually need multi-user real-time sync, team reporting, and priority support. Until then, the free tier is the whole product.

A note on what ToolBerry is not, because we'd rather be honest

We're not going to pretend ToolBerry is a drop-in replacement for ServiceTitan. It isn't. If you run twenty trucks, three dispatchers, and a 24/7 call center, you should be on a different platform.

What ToolBerry is: the best free tool we know how to build for a solo operator or small crew that has been waiting for an honest on-ramp. The kind of tool you can install on your phone tonight, load five customers into in fifteen minutes, and run a real route on tomorrow morning. Without giving anyone your email.

How to actually start

If you're a landscaper in Escondido, Vista, San Marcos, Chula Vista, El Cajon, Oceanside, Carlsbad - or anywhere else in San Diego County, or anywhere in SoCal, or anywhere in the country, frankly - here's what to do.

1. Go to toolberry.net on the device you live in. The site detects whether you're on iPhone or Android and routes you to the right place.
2. Or grab it directly from the App Store or Google Play.
3. Open the app. Don't sign up. There's nothing to sign up for. Just start.
4. Add your three trickiest customers - the ones with the gate codes you can never remember, the ones with the weird recurring schedules, the ones who keep asking what you did last spring.
5. Run a route with it tomorrow. See if it survives a real day.

If it doesn't work for you, you're out exactly zero dollars and zero contracts. If it does, keep going. Tell the next landscaper at the gas station off the 78. We're trying to build a tool that the trade actually owns, not the other way around.

One more thing

There's an honest version of this story that doesn't get told enough: small landscaping businesses in Southern California are quietly running some of the most beautiful properties in the country. They are family operations that paid for college tuitions and mortgages and trips back home and three trucks instead of one. They are, in the most literal sense, the people who keep this place green.

They deserve tools that respect them. Tools that don't condescend, don't extract, don't demand an email and a contract before they prove their worth, and don't break when the signal drops behind a hedge. Tools that work in Spanish and English without making it a big deal. Tools that fit in the truck, not the conference room.

That's the whole reason ToolBerry exists. To give Carlos in Escondido - and the thousands of Carloses across SoCal and beyond - a tool he can pick up if and when it helps, on his own terms, with his own data, on his own phone. Use as much or as little of it as fits your day. The clipboard isn't going anywhere on our account.

That's the bet we're making, and it's the bet we're asking you to make with us.

If you've read this far, you're either Carlos or you know him. Either way: the next move is the same. Open the app. Schedule a job. See what changes.

We'll meet you on the truck.

Get ToolBerry — it's free forever →

No account. No credit card. Works offline.

Have a question?

We're always happy to talk to people running real businesses on this stuff. Reach out at contact@toolberry.net.

That moment is the whole reason ToolBerry exists.

Most field service apps treat the network like it's always there, and "offline mode" like it's a backup plan for when things go wrong. ToolBerry is the opposite. The network is the backup plan. Your device is the source of truth. That's what we mean by offline-first, and it's not a feature we tacked on — it shapes almost every decision we make about the product.

Here's why we built it that way, and what it actually means for you.

What "offline-first" actually means

There's a distinction worth making up front, because the term gets used loosely.

Offline-tolerant apps assume the cloud is the source of truth. They cache some data so you can keep working when the signal drops, but the moment you lose connection, the experience degrades — features stop working, screens go blank, and you're nervous about whether anything you typed will survive.

Offline-first apps assume the device is the source of truth. The cloud is a sync target, not a dependency. Whether you have five bars of LTE or you're sitting in a basement utility room with no signal at all, the app behaves identically.

ToolBerry is the second kind. Your jobs, customers, sites, contacts, assets, and schedules live in a real database on your phone — not a cache, not a queue waiting to talk to a server. We use SQLite, the same database engine that powers most of the apps already on your phone. There's more on the technical side at the bottom of this post if you're curious.

The obvious reasons: speed and reliability

If you've worked in the field for any length of time, you already know these:

Your signal is unreliable, but the work isn't. Basements. Industrial buildings. Rural properties. Underground parking. Anywhere with metal walls. Field work happens in places that weren't designed with cell towers in mind. An offline-first app doesn't care.

Speed. Reading from your local device is roughly a thousand times faster than waiting for a server round-trip. Loading a customer's history, jumping into a work order, searching across hundreds of jobs — it's all instant, because nothing is being fetched. There's no loading state for your own data. It just shows.

No "saving…" anxiety. Every change you make is written to your device immediately. No half-saved state, no "are you sure you want to leave this page?", no risk of losing what you typed because the connection blinked.

These are the table-stakes reasons. They're the ones every offline-first pitch leads with. The more interesting reasons are the less obvious ones.

The less obvious reasons (which are arguably the bigger ones)

Your data is yours, not ours

Most SaaS tools work like this: you type your customer's name, address, and phone number into a form, and that information gets shipped off to a server in someone else's data center. You're trusting that company with your customer relationships — and if they have an outage, get acquired, change their pricing, or decide to use your data in ways you didn't anticipate, you don't have much recourse.

ToolBerry's free tier inverts that. Your customers, sites, and job history sit in a database on your device. We don't have it. We can't lose it, leak it, sell it, or hold it hostage. If we disappeared tomorrow, your data would still be on your phone.

For solo operators and small crews — especially in industries where the customer list is the business — that's a meaningful difference. You're not renting access to your own information.

"Free forever" is structural, not promotional

Every field service tool you've evaluated has a problem they don't talk about: every free user costs them money. Servers, databases, bandwidth, support — it adds up. So they cap the free tier hard and push you toward paid plans the moment you start finding the product useful. Heroku had a famously generous free tier and ended up killing it entirely in 2022 for exactly this reason.

When we say ToolBerry is free for life for solo operators, we can mean it because a free user genuinely costs us close to nothing. No server holding your data, no database we're paying to keep running, no per-user infrastructure bill. The app on your device does the work.

That changes what the free tier can be. Instead of a stripped-down trial designed to push you to upgrade in 30 days, it can actually be the full product for people who don't need team sync. You upgrade when the business need genuinely changes — when you hire a second tech, when you want QuickBooks integration, when you need cross-device sync — not because we've artificially throttled you. The paywall is aligned with your business growing, not with our server bill.

For reference: typical FSM competitor pricing starts around $169/month and runs to $250–$500 per technician per month at the enterprise end. We can be radically cheaper because our cost structure is radically different.

Your uptime isn't tied to ours

When your scheduling app goes down for two hours on a Tuesday morning, the whole crew is stuck. You've all built workflows around a tool that suddenly isn't there. With ToolBerry's free tier, this category of problem doesn't exist — the app on your phone keeps working regardless of what's happening on our end.

Even on paid tiers, where sync becomes part of the picture, the local-first model means a backend hiccup degrades sync, not the app itself. You keep working. Sync catches up later.

Battery and data plan friendly

Offline-first apps don't constantly chatter with a server. No background polling, no keepalive connections, no "checking for updates" every thirty seconds. That's quietly easier on your battery and your data plan, especially if you're tethering on the road or running on a budget carrier with a tight cap.

No signup means no friction

This isn't strictly because we're offline-first, but it's only possible because we are. Since your data lives on your device, we don't need a server account to identify you — which means no email, no password, no SMS verification, no onboarding wizard. Open the app, start adding jobs.

The number of free trials people abandon at the signup screen is staggering. We just removed the screen.

The honest tradeoffs

Offline-first isn't free. There are real tradeoffs, and we'd rather be straight about them than pretend they don't exist.

Multi-device sync is a paid feature. If you want the same data on your phone, your tablet, and your office computer, you need either our optional Dropbox-based backup or our paid Team tier. Real-time multi-device sync requires a backend, and backends cost money. We're not going to pretend otherwise by burying that cost in everyone's monthly fee.

Backups are your responsibility on the free tier. If you lose your phone and you haven't connected Dropbox or upgraded, your data goes with it — same as if you lost a paper notebook. We make this easy to mitigate (Dropbox backup is free and takes about thirty seconds to set up), but we want you to know it exists.

Initial app size is larger. Offline-first means we ship the database engine, your full schema, and enough infrastructure to run independently. The app is a few megabytes bigger than a thin-client equivalent. You'll feel this once, on install.

Browser private/incognito modes block it. Browsers intentionally prevent persistent local storage in private modes, which means ToolBerry can't save anything in those windows. We've written about this separately — there's a dedicated post on it — but it's worth flagging here as part of the honest picture.

Some advanced features genuinely need a backend. Real-time team coordination, dispatcher views, cross-tenant work order routing, accounting integrations — these aren't features we're holding back behind a paywall as a gimmick. They actually require a server. Offline-first solves a huge chunk of the problem space, but it's not a universal answer, and we're not going to tell you it is.

What this means for you

If you run jobs from a truck: ToolBerry behaves the same whether you're parked in a downtown garage or out at a rural property with no service. There's no online or offline mode to be aware of — there's just the app, and it works.

If you manage scheduling, dispatch, or operations from an office: the local-first model means the people in the field can actually rely on the tool you're handing them. Their data entry doesn't disappear into a sync queue you can't audit. Their app doesn't lock up when their connection blips. And when you're ready to coordinate across a team, the paid tiers are built on the same foundation — sync layered on top, not bolted on.

If you're evaluating ToolBerry against incumbents: the architecture is a different category, not an incremental improvement. The cost model, privacy posture, and field reliability all flow from the same core decision. That's worth weighing carefully.

Have a question?

We're always happy to talk through how this works for your specific situation. Reach out at contact@toolberry.app.

For the Technically Curious

If you want to understand how this is actually built, here's the picture under the hood.

SQLite on the device

ToolBerry uses SQLite as its local database — the same engine that ships inside iOS, Android, Chrome, Firefox, macOS, and most consumer applications you use daily. It's not a cache. It's not localStorage. It's a real relational database with full SQL support: joins, transactions, indexes, foreign keys, the works. We've tested it with hundreds of thousands of records on commodity phones and the performance stays flat.

On native iOS and Android, SQLite is accessed through the standard system APIs via Capacitor. In the browser/PWA, we use a build of SQLite compiled to WebAssembly, persisted to disk via OPFS (Origin Private File System) — a relatively new browser API designed for exactly this kind of use case.

Why SQLite over IndexedDB or localStorage

Most web apps with offline mode use IndexedDB or localStorage. Both have limitations:

• localStorage is a key-value store with a hard ~5 MB cap and synchronous I/O on the main thread. Unusable for any meaningful dataset.
• IndexedDB is more capable but has a famously awkward API, no SQL, weak cross-browser consistency, and known reliability issues.
• SQLite over OPFS gives us real SQL, real transactions, predictable behavior across platforms, and the same query layer we share with our backend. It's the only option that scales to a real production dataset without compromise.

How sync (eventually) fits in

Free-tier users are fully offline by design. Paid tiers add sync, and the architecture is built around the device being authoritative:

1. Every write goes to the local SQLite database first, immediately, with no network involved.
2. Writes are also recorded in a local outbox.
3. When the device is online and the user is on a paid tier, the outbox flushes to our backend.
4. Changes from other devices arrive as a stream and merge into the local database.

This is the same broad pattern used by Linear and most modern local-first collaborative apps. It means the local app never blocks on the network, and sync becomes a background concern rather than a critical path.

Why the cost structure is so different

A traditional FSM SaaS hosts every customer's data in a central database, runs API servers per request, and pays for storage, compute, and bandwidth on every interaction. The marginal cost per free user is real, and at scale it dominates.

ToolBerry's free tier is a static SPA served from a CDN — bandwidth costs measured in fractions of a cent per user — and all data lives on user devices. There's nothing for us to host beyond the app bundle itself. Paid tiers reintroduce backend infrastructure for sync and integrations, but only for the users who actually need it.

This is the structural reason "free forever" works for us when it didn't for Heroku. They were paying real per-user infrastructure costs and trying to recoup them through conversion. We're not.

Further reading

• Why ToolBerry Doesn't Work in Incognito or Private Mode — the browser caveat in detail
• SQLite — When To Use
• MDN — Origin Private File System
• Local-First Software — You Own Your Data, In Spite of the Cloud — the academic case for this architecture pattern