DEV Community: SilentCore Software

Custom database vs spreadsheets for small business: when it is time to switch

SilentCore Software — Tue, 10 Nov 2026 10:47:21 +0000

Originally published at silentcoresoftware.com.

What spreadsheets do well

Be honest about the strengths first. Spreadsheets are unbeatable for one person analyzing data, for prototypes, for one-off calculations and for small lists that change rarely. If one or two people use the file and mistakes are cheap, keep the spreadsheet. Building software to replace it would be waste.

Eight signs you have outgrown spreadsheets

Version conflicts. “Final_v3_JM.xlsx” exists, or people overwrite each other in a shared sheet.
No permissions. You cannot let staff see orders without also seeing margins or salaries.
No history. When a number is wrong, nobody can tell who changed it or when.
Fragile formulas. One person understands the formulas, and everyone is afraid to touch them.
Duplicates. The same customer appears three times with different spellings.
Copy-paste between tools. Data is retyped into QuickBooks, the CRM or email every day.
Size and speed. Files take minutes to open or hit row limits.
Field access. People on site need the data on a phone, and the spreadsheet is unusable there.

Three or more of these, with more than a handful of people depending on the data, usually means the spreadsheet costs more in errors and hours than it saves.

The options in between

Option	Good for	Limits
Shared Google Sheets / Excel online	Small teams, simple lists	Weak permissions, no relational integrity
Airtable, Smartsheet and similar	Light relational data, quick setup	Per-seat pricing, record limits, logic gets complex, vendor lock-in
Microsoft Access / FileMaker	Single-office desktop databases	Poor fit for remote teams, browsers and integrations; shrinking talent pool
Low-code platforms	Internal forms and simple workflows	Per-user cost, platform limits on complex logic
Off-the-shelf software	Standard processes (CRM, accounting, inventory)	You adapt to the product
Custom database + web app	Specific data, rules and integrations	Upfront build; needs an owner on your side

Try the cheapest option that fits. Many businesses should move from spreadsheets to an off-the-shelf product, not to custom software. Custom is the right call when your data model is specific to your business, when several systems must share one source of truth, or when per-seat tools become expensive as the team grows.

What a custom database project looks like

Collect every spreadsheet and report; list the real entities behind them.
Design the data model in PostgreSQL and review it in plain language.
Build a web interface with role-based permissions and an audit log.
Migrate and clean the data, reconciling totals with the original files.
Add reports, exports and integrations with accounting and other tools.

A focused database for one department typically takes 4–6 weeks; larger systems with several roles and integrations 8–10 weeks or more. See custom database development and business automation.

A quick self-test

Answer yes or no: more than five people edit the data; you need different access for different roles; mistakes cost money or customers; the data is re-entered into another system; people need it on a phone in the field; you need to know who changed what. Four or more “yes” answers mean a proper database will pay for itself in fewer errors and fewer hours. Two or fewer — keep the spreadsheet and revisit in a year.

Keep spreadsheets where they belong

Moving to a database does not mean banning spreadsheets. The best setups export clean data from the database into a spreadsheet for analysis — the database becomes the source of truth, and the spreadsheet goes back to doing what it does best. Related: what drives the cost of a custom CRM, internal dashboards case study.

Questions we are asked most

When should a small business switch from Excel to a database?

When several people depend on the same data and you see version conflicts, missing permissions, no change history, duplicates or daily retyping between tools. One or two users with low-stakes data can stay on spreadsheets.

Is Airtable a database?

It is a hosted relational tool with a spreadsheet-like interface. It is a good middle step for light data; teams usually outgrow it when logic gets complex, records grow or per-seat costs rise.

Is Microsoft Access still a good choice?

For a single office on Windows it still works, but it fits poorly with remote teams, browsers, phones and integrations. Most Access replacements move to a web app on PostgreSQL or SQL Server.

Can we still use Excel after moving to a database?

Yes. Exports and live connections let you analyze data in Excel or Google Sheets while the database stays the single source of truth.

SilentCore Software builds custom CRMs and business software for service companies. Read the full guide with up-to-date tables on our site.

Field service CRM features: a practical checklist for 2026

SilentCore Software — Tue, 10 Nov 2026 10:40:55 +0000

Originally published at silentcoresoftware.com.

Must-have features

One customer and property record with every job, call, estimate, invoice and photo at that address.
Request intake from phone, web forms and marketplaces without retyping.
Dispatch board by technician and day, with drag-to-reschedule and live updates.
Technician mobile app with job details, notes, checklists, photos and signatures.
Offline mode for basements, rural sites and poor coverage.
Estimates on site with options the customer can approve.
Invoicing and payments by card or link, right after the job.
Accounting sync with QuickBooks or your accounting system, both directions where needed.
Recurring service — maintenance agreements that create visits and reminders automatically.
Customer notifications — confirmations, on-the-way texts, reminders.
Roles and permissions for owners, office, technicians and subcontractors.
Reports you actually use: jobs, revenue per technician, unpaid invoices, callbacks.

Nice-to-have features

Route optimization (valuable with many daily stops, less so for long jobs).
Inventory per truck and parts ordering.
Customer portal with history and invoices.
Call tracking and recordings on the customer record.
Marketing campaigns and review requests.
GPS fleet tracking.

Nice-to-haves are where subscription tiers and add-ons grow. Decide which you will really use before comparing prices.

Questions to ask in every demo

Show me a job that needs two visits and a second technician. How is it scheduled and invoiced?
What does the technician see offline, and what syncs when they reconnect?
Show the QuickBooks sync for an invoice that is edited after it was sent.
How do I get all my data out, in what format, and at what cost?
Which of the features you showed are in my tier, and which are add-ons?
What did the price do at renewal for customers like us?

Features that signal you need custom

If your must-have list includes things no platform does the way you work — commercial contracts with progress billing, construction-style job costing, multi-trade jobs, special dispatch rules, an integration with a niche system, or a workflow unique to your trade such as fireplace installs and annual sweeps or glass orders with long lead times — a custom system may fit better. We cover that path on custom field service CRM.

Mistakes we see most often

Buying for the demo, not the dispatcher. Polished marketing modules impress owners; the dispatch board decides whether the office is happy.
Ignoring data migration. Ask early how customers, equipment history and open invoices will move.
Skipping the technician test. Give the app to one technician for a week before signing.
Underestimating accounting sync. Edited invoices, partial payments and credits are where most sync problems appear.

How to run the evaluation

Write down your top three daily workflows step by step.
Make every vendor (and any custom developer) walk through those workflows, not their standard demo.
Ask a dispatcher and a technician to join the demos — they will spot problems in minutes.
Compare five-year total cost, not monthly price: TCO worksheet.

Questions we are asked most

What features should a field service CRM have?

At minimum: a customer and property record, request intake, a dispatch board, a technician mobile app with offline mode, on-site estimates, invoicing and payments, accounting sync, recurring service, customer notifications, roles and reports.

Do I need route optimization?

Only if technicians make many short stops a day. For long jobs or small service areas, a good dispatch board matters more.

What is the difference between field service CRM and field service management software?

In practice the terms overlap. FSM emphasizes scheduling, dispatch and mobile work; CRM emphasizes customers and sales. A good system for a service company does both on one record.

How do I compare a platform with custom software?

Walk both through your own top workflows and compare five-year total cost, including add-ons, workarounds, hosting and support.

SilentCore Software builds custom CRMs and business software for service companies. Read the full guide with up-to-date tables on our site.

How much does a custom CRM cost in 2026? What really drives the price

SilentCore Software — Tue, 10 Nov 2026 10:40:10 +0000

Originally published at silentcoresoftware.com.

The short answer

The price of a custom CRM is the number of engineer-weeks it takes multiplied by the team’s rate, plus hosting and ongoing support. Rates vary by country and seniority far more than by vendor marketing. So the useful question is not “what does a CRM cost” but “how many weeks of work is my CRM”. That number is driven by six things.

The six cost drivers

Driver	Smaller effort	Larger effort
Core modules	Contacts, pipeline, tasks	Jobs, dispatch, estimates, invoicing, project finance
Integrations	Email and calendar	Accounting, telephony, marketplaces, payment providers, legacy systems
Roles & permissions	One office team	Several departments, field staff, partners or customer portal
Data migration	One clean spreadsheet	Several systems with duplicates and years of history
Mobile	Responsive web only	Native-quality iOS/Android app with offline mode
Reporting	A few fixed reports	Role-based dashboards and finance exports

Integrations are the driver buyers most often underestimate. A clean, well-documented API such as QuickBooks Online is predictable; a phone system with webhooks is moderate; a legacy desktop system with no API can be the most expensive part of the project. Ask every vendor to estimate integrations as separate line items.

Typical timelines as a proxy for cost

From our own projects: a focused CRM with pipeline, tasks and one or two integrations is usually live in about 6 weeks; a field-service style CRM with dispatch, estimates, invoices and QuickBooks sync in 8–12 weeks; a companion mobile app adds about 4 weeks. Discovery takes 1–2 weeks before any of that. Multiply the weeks by the size of the team (typically two to three engineers) and by the rate of the vendor you are considering, and you have a realistic range.

Comparing build vs subscription honestly

A per-user SaaS fee looks small next to a build. Over five years it rarely is, but the comparison must include everything:

SaaS 5-year cost = (monthly fee per user × users × 60) + add-ons + implementation partner + price increases + the hours your team spends on workarounds.
Custom 5-year cost = build + hosting × 60 months + support and improvements per year × 5 + your own time for product decisions.

If the SaaS fits your process, it usually wins for teams under ten users. Custom tends to win when headcount is growing, when you pay for several overlapping tools, or when workarounds cost real office hours every week. Run your own numbers with the total cost of ownership worksheet.

Hidden costs to ask about

Support after launch. Plan for ongoing maintenance: security updates, dependency upgrades, small changes. Software that nobody maintains decays.
Hosting. For a typical small-business CRM, cloud hosting is modest; ask for an estimate in writing and make sure the account is in your name.
Third-party fees. SMS, telephony, e-signature and payment providers charge per use, whether you build or buy.
Your team’s time. Someone on your side must answer questions and review demos — roughly a few hours a week.
Change requests. Agree how scope changes are priced before the build starts.

Safe ways to reduce the cost

Build the 20% of features the team uses every day; keep using specialist tools for the rest and integrate them.
Start with a responsive web app; add a native mobile app once the workflow is proven.
Clean your data before migration — duplicated customers are expensive to fix in code.
Pay for a separate discovery phase. A written specification makes every later quote comparable and cuts surprises.

Red flags in a quote

A fixed price given before anyone has seen your process.
Integrations described as “included” without naming the systems.
Code, hosting or data kept in the vendor’s accounts.
No line for support after launch.

We do not publish prices on this site; every project gets a written scope and estimate after a short call and discovery. More context: custom CRM development, custom CRM vs Salesforce, how to choose a development company.

Questions we are asked most

How much does a custom CRM cost?

It equals the engineer-weeks required multiplied by the team’s rate, plus hosting and support. A focused CRM is roughly 6 weeks of work for a small team; a field-service CRM with dispatch and accounting integration is 8–12 weeks; a mobile app adds about 4.

Is a custom CRM cheaper than Salesforce or HubSpot?

Not always. For small teams with a standard process, SaaS is usually cheaper. Custom tends to be cheaper over five years when user counts grow, several overlapping tools are replaced, or workarounds cost significant staff time.

What is the most expensive part of a custom CRM?

Usually integrations with legacy or poorly documented systems and data migration from several messy sources — not the screens themselves.

What ongoing costs should we expect after launch?

Hosting, third-party usage fees such as SMS or telephony, and a support arrangement for updates, fixes and small improvements.

Why do quotes for the same CRM vary so much?

Vendors assume different scope, team seniority and rates. A written specification from a discovery phase makes quotes comparable.

SilentCore Software builds custom CRMs and business software for service companies. Read the full guide with up-to-date tables on our site.