Can I build my own CRM with Claude or ChatGPT, and will it hold up for my team?

By Ranjit Bhinge, founder of Blur Studio · Updated · 7 min read

Short answer: Yes, you can build a working CRM (customer relationship management tool, the place you keep contacts, deals and notes) with Claude or ChatGPT, and for one person with simple needs it often works. It gets risky when a team shares it, when it holds real client data, or when it must connect to email, invoicing or a website form. The usual failure is not that it looks wrong. It is that nobody has checked who can see which records, and nobody keeps it running.

Ranjit Bhinge

You have seen people build a CRM in a weekend with an AI tool and you want to know if yours would survive real clients and a real team.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

The short version

An AI tool can write the screens, the database and the logic for a basic CRM. That part is real. What it cannot do for you is decide who should see what, test what happens when two people edit one record, run backups, keep the thing patched, or fix it at 7am when a form stops working. Those are the parts that decide whether a homemade CRM is an asset or a liability.

My rule: build it yourself if it is only you (or you and one trusted person), the data is low-sensitivity, and you can live with it breaking for a day. Pay for a ready-made tool or get it built properly if any of those are false.

What AI builds well

If you describe your process clearly, tools like Claude, ChatGPT, or an app builder (a tool that turns a plain-English description into a working web app, such as Lovable or Replit) can produce:

  • A contact list with notes, tags and search.
  • A deal pipeline with stages you can drag cards between.
  • Reminders and a "who to contact today" view.
  • A simple form that adds contacts.
  • Basic reports, such as deals by stage or by month.

A simple version can live in a spreadsheet or in a small web app. The newer approach, sometimes called "vibe coding," means describing what you want in plain English and letting the AI write the code. I wrote a plain guide to vibe coding for business owners, and a longer one on whether you can build a real business app with AI.

What breaks when a team starts using it

1. Who can see what

This is the big one. OWASP, the nonprofit that publishes the standard list of web security risks, ranks broken access control as the number one risk in its 2021 Top 10. It means users can act outside what they should be allowed to, for example by changing a number in a web address and seeing someone else's record. AI-written code often works perfectly on screen and still lets anyone who knows the address see everything.

If your app uses Supabase, a popular hosted database that many AI builders connect to, the details matter. Supabase's own documentation says a table in an exposed schema without Row Level Security (RLS, rules inside the database that decide who can read or change each row) is readable and writable by any role with a grant on it, and that on existing projects a new table in the public schema starts with every privilege already granted. Once RLS is switched on, no data is reachable through the API with a publishable key until you write policies. Whether those policies exist and are correct is exactly the kind of thing a person has to check. My AI-built app security checklist lists the checks.

2. Real client data

The FTC's guide for businesses on protecting personal information has five principles: know what you hold, keep only what you need, lock it, dispose of it properly, and plan for incidents. A CRM holds names, phone numbers and often notes about a person's circumstances. If you are in health, finance or law, or sell to people in the EU or UK, stricter rules apply. This is not legal advice. Ask a lawyer before you put sensitive records in a tool you built.

3. Connections to other tools

A CRM on its own is a notebook. It becomes useful when it connects to your inbox, your calendar, your invoices and your website form. Each connection is a point where logins expire, formats change and data goes missing without an error message. Prototypes rarely handle this well.

4. Two people, one record

If two people edit the same contact at the same time, whose change wins? Mature tools have decided this. A homemade one usually has not.

5. Upkeep and ownership

Someone must fix it, back it up and update it. If you built it with a chat tool, that someone is you, and the knowledge of how it works is in a chat history. The article on whether a vibe-coded app is ready for production goes through what "ready" has to mean.

A decision rule you can use

Your situationWhat I would do
Just you, under a few hundred contacts, low-sensitivity dataA spreadsheet or a free CRM first. Build only if you have a need no tool meets.
You and one trusted person, a real workflow no tool fitsBuild with AI, with the checks below, and keep an export you can restore from.
A team of 3 or more sharing itUse a ready-made CRM, or have the build done and checked by a developer.
Health, finance, legal or children's dataDo not DIY the data layer. Use a vendor with the right compliance, or hire someone accountable.
Must connect to email, invoicing and a website formCheck whether a ready-made CRM already connects. Build only for gaps.

What a ready-made CRM costs, for comparison

Before you build, price the alternative. HubSpot, a widely used CRM, has a free tier that allows up to 2 users and 1,000 contacts, and its Starter plan is listed at $20 a seat a month standard, with a lower first-year rate for new customers (as of November 2026; check HubSpot's page for the current figure). My guide to CRMs for small business compares more options.

A homemade one has running costs too. Supabase's Free plan gives a 500 MB database, 1 GB of file storage and 50,000 monthly active users, but limits you to 2 active projects and pauses projects after a week of inactivity. Its Pro plan starts at $25 a month (as of November 2026). Hosting on Vercel, a service that publishes web apps, costs $20 a month per developer seat on its Pro plan, and its free Hobby plan is for personal, non-commercial use only. So a business CRM you built and run yourself plausibly costs $45 a month or more before you count your time, whereas a free CRM tier costs nothing. For the wider comparison, read build versus buy software and how much vibe coding costs.

A worked example: weekend build versus production build

These figures are made up to show the gap.

The weekend build. A solo consultant describes her pipeline to Claude and gets a web app with contacts, deals and a "follow up today" list. It takes 10 hours over a weekend. She uses it alone with about 150 contacts. It works. Cost: her weekend and about $45 a month in hosting and database.

The same app, three months later. She hires an assistant and a part-time salesperson. Now the questions begin. Can the assistant see deal values? Does the salesperson see her old clients? What happens when the assistant deletes a contact by mistake? There is no undo and no backup she has tested. The app has no login for the salesperson, so she shares one password. This is the point where I would stop and either move to a ready-made CRM or get the app checked and finished.

Checklist before real client data goes in

  1. Every person has their own login. No shared passwords.
  2. Access rules are written down. For each role, what they can see and change.
  3. Test the rules. Log in as a low-access user and try to open another user's record by changing the address, as in OWASP's example of parameter tampering.
  4. Database protection is on. If you use Supabase, RLS is enabled on every table and policies are written.
  5. Secret keys are not in the page. Supabase says a secret key can bypass RLS, so keep it out of the page and the app code a browser downloads.
  6. Backups exist and you have restored one. A backup you have never restored is a hope.
  7. You can export everything to a spreadsheet at any time.
  8. Someone owns upkeep. A named person and a reserved hour a month.
  9. You have a plan for a breach. Who you tell, and how fast.

A person must check the access rules and backups. An AI can help you write a test list, but it cannot confirm that your live data is safe.

How to start if you decide to build

  1. Write one page: who uses it, what they do each day, what data it holds.
  2. List the five things it must do, and what it must not do.
  3. Ask Claude for a simple data model (the list of things it tracks and how they connect) and read it before any code is written.
  4. Build the smallest version, with your own data only, for two weeks.
  5. Only then add a second user, with access rules first.

When to hire someone to finish it

Get help when you have a working prototype and any of these are true: a second person needs access, real client data is going in, it must connect to other tools, or you would be in real trouble if it was down for a day. At that point the job is usually fixing and finishing, not starting over. Blur Studio fixes and finishes start around $1,500, depending on what is there.

How I'd approach this

I would build the first version myself with an AI tool. It is the cheapest way to find out what you actually need, and it teaches you your own process. I would treat that first version as a prototype, not a product.

I would not put real client data in it until the checklist above is done. And I would never let the choice be "homemade or nothing." If a free tier of a ready-made CRM does the job, use it and save your energy for the work that makes you money.

If you have a prototype that works and you want it checked, secured and finished so it can carry a real team, or you want one built from scratch around how you work, talk to me.

Questions people ask

Can Claude build a CRM for me?

Claude can write a basic CRM, including contacts, deals and reminders, from a clear description. It cannot check that your live data is protected or keep it running. Read my guide to building a real business app with AI for what that gap looks like.

How long does it take to build a CRM with AI?

A basic single-user version can take a weekend. A version a team can safely share usually takes much longer, because the access rules, testing, backups and connections take more effort than the screens.

Is an AI-built CRM secure?

Not by default. Broken access control is the number one risk in OWASP's 2021 Top 10, and database rules such as Supabase Row Level Security must be switched on and written correctly. Use the AI-built app security checklist before real data goes in.

Should I build my own CRM or buy one?

If a free or cheap ready-made CRM covers your needs, buy. Build only when you have a workflow no tool fits. See build versus buy software for a fuller decision guide.

How much does it cost to run a homemade CRM?

Hosting and database can run around $45 a month for a business setup (Supabase Pro from $25 and Vercel Pro at $20 per developer seat, as of November 2026), plus your time. A free HubSpot tier allows 2 users and 1,000 contacts at no cost.

Is a vibe-coded app ready for real customers?

Sometimes, after checking. The article on whether a vibe-coded app is production ready lists what must be true first.

More in this topic: Problem solving: custom software (22 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…