For a lot of teams, the "CRM" is actually one Excel file everybody takes turns opening.
That file usually has a few symptoms: someone edits somebody else's column, versions are scattered across different people's laptops, follow-up notes pile up into one long string in a notes field, and nobody really knows which copy is current.
NocoDB is the sensible next step from that spreadsheet. But it is not Salesforce, and that needs saying up front.
30-second overview
| Item | Details |
|---|---|
| What it solves | Turning "the Excel file everyone takes turns opening" into a system |
| Biggest advantage | The API is the default, not a paid add-on |
| What it can't do | Automatic email logging, opportunity scoring, marketing automation |
| Who it suits | Teams whose process is still changing and whose product isn't standardized |
| Signal to move on | Maintaining the tables themselves starts eating serious time |
What NocoDB as a CRM can actually do
Moving your customer list out of a spreadsheet and into NocoDB fixes several of those symptoms outright:
- Linked fields replace copy-paste. Customers, contacts, follow-up notes and quotes can be four tables joined by relations. Open one customer and you see every interaction beneath it, instead of cramming ten columns into a single row.
- One set of data, several ways to look at it. Sales wants a Kanban board (drag by stage), the manager wants a grid (sort by value), support wants a calendar (by follow-up date) — that's three views, not three files.
- Forms write straight into the database. The enquiry form on your website can be a NocoDB form view, so a submission is a record and nobody has to retype it.
- Automatic REST API and webhooks. Every table gets an API automatically, so n8n can send a notification when a new customer appears, email someone when a status changes, or sync the data into another system.
That last point is NocoDB's real advantage over a conventional CRM: it assumes you will want to connect your data to somewhere else. Closed CRMs are generally not designed that way.
What it won't give you
Worth listing honestly — it's more useful than listing the upsides:
- No sales methodology out of the box. A mature CRM has a whole set of process assumptions built in — deal stages, forecast formulas, activity tracking. NocoDB gives you blank tables and leaves the process design to you. That is freedom, and it is also work.
- No built-in marketing automation. Email sequences, open-rate tracking, behavior-based segmentation — you assemble those from external tools (connecting n8n, for example).
- No automatic logging of calls and emails. When a rep phones or emails a customer, it doesn't show up under that customer by itself; someone has to add it. In practice this is the link that breaks most easily.
When NocoDB is actually the better choice
Not every team should be on a real CRM. In these situations NocoDB is the more correct answer:
- Your sales process is still changing. A mature CRM's value comes from its established process, but if you adjust yours every couple of months, that established process becomes friction. Blank tables are much faster to change.
- What you sell isn't standardized. Project work, custom work, businesses where every quote is different — forcing that into a standard CRM's opportunity fields is usually painful.
- You need it wired into automation. NocoDB's API is there by default, not as a paid add-on.
- Only a handful of people use it. With a team of five or fewer, keeping data quality up by mutual understanding is workable.
Signals it's time to move on
Rather than looking at team size, look at these specific signals. Two or more of them and it's time to seriously evaluate a dedicated CRM:
| Signal | What it means |
|---|---|
| People start "forgetting to update" and nobody notices | Data quality depended on discipline, and the discipline has run out |
| You need to hide certain customers or fields by permission | Permission requirements are getting granular, and a general-purpose tool starts to strain |
| You need automatic tracking of email and call history | That's a core feature of a dedicated CRM; building it yourself is expensive |
| You need forecasting and funnel analysis reports | What you want is a methodology, not just data |
| Maintaining these tables starts eating serious time | The license fee you saved has already been eaten by hours |
That last one is the most practical test. With a system you assembled yourself, the cost isn't the license — it's the person who maintains it. When that person starts to find it a chore, it's time to switch.
Start with one table
If you decide to try it, don't design the complete data structure on day one.
The approach that tends to work is: import your existing Excel exactly as it is, use it for two weeks, and see what people actually complain about. Those complaints are the relations and views you should design first. Teams that draw the whole architecture before rolling out usually end up with a beautiful system nobody uses.
RoamerHost's managed NocoDB plan is NT$499/mo (1 vCPU / 5 GB), including SSL and a dedicated subdomain, with the data living in your own instance.
The first step in moving off Excel
Don't design the complete data structure at the start.
The approach that tends to work: import your existing Excel exactly as it is, use it for two weeks, and see what people actually complain about. Those complaints are the relations and views you should design first.
Common complaints and what they call for:
| Complaint | What to do |
|---|---|
| "I can't find where we left off last time" | Split follow-up notes into their own table and join it by relation |
| "I don't know who to contact first" | Add a stage field and open a Kanban view |
| "I only want to see my customers" | Give each person a view filtered by owner |
| "I keep forgetting to follow up" | Add a next-contact date and set an automated reminder |
Teams that draw the full architecture before rolling out usually end up with a beautiful system nobody uses.
FAQ
Q: How is this different from a proper CRM?
A mature CRM has an entire sales methodology built in — deal stages, forecast formulas, activity tracking. NocoDB gives you blank tables and leaves the process to you. That is freedom, and it is also work.
Q: Can it log email correspondence automatically?
Not built in. You wire it up yourself with automation, and this is usually the weakest link in a DIY CRM — because it requires someone to remember every single time, or the automation to succeed every single time.
Q: How many users is it good for?
Rather than a headcount, watch for the signal: once people start "forgetting to update" and nobody notices, keeping data quality up by discipline has stopped working.
Q: Can I move the data into a proper CRM later?
Yes — the data is yours and it exports. Use a clean field structure from the beginning and the eventual migration will be much simpler.
Q: What's the single most worthwhile thing to build first?
Add an automated reminder on the next-contact date. It has the highest return of anything here — it's the only feature in the whole system that comes looking for you.
Sources and further reading
For field types and the permission model, the official documentation is the authority:
Further reading
- NocoDB for inventory management: how small teams actually do it
- NocoDB intro: the open source Airtable alternative
- NocoDB guide: building your first table and view
- NocoDB API quickstart: getting a token, reading and writing tables, connecting automation
- NocoDB vs Airtable: data ownership, record limits and a real cost comparison
- RoamerHost NocoDB hosting plans
Want someone to build it for you?
Once the data volume grows, or you need to plug this into your company's existing systems, it stops being just a question of picking a tool. Roamer Tech takes on enterprise system customization and API integration:
