Build a customer database you actually own
Stop scattering customers across a trial CRM, an Excel export, an email list, and a support inbox. Publish one database with the schema you want, the fields that matter, and exports any time.
No credit card required · Published in minutes
See how it works ↓Why this is harder than it should be
Customer information lives in four places at once: a half-set-up CRM trial, an Excel file someone exported last quarter, an email-marketing list with stale segments, and a support tool with its own contact records. None of them agree. None of them are owned outright. The team works around the chaos by emailing each other for the latest version, and the founder cannot answer a basic question: who are our customers, and how many do we actually have?
What you can build from one prompt
The shape varies — Exepad publishes whichever you describe.
A unified customer record with the fields your business actually uses.
A signup form that writes directly into the database, not a SaaS silo.
A search and filter view across every customer and segment.
A tag and segment system for campaigns, regions, or lifecycle stages.
A REST and MCP endpoint other apps and AI tools can query.
An export-to-CSV button that works on every record, every time.
What this might look like
Three real users, three different outcomes — same platform.
A bootstrapped SaaS founder
1,400 customers, 1 source of truth
The founder describes the customer fields that matter — email, plan, signup date, last-active date, MRR. Exepad publishes a database with a list view, segment filters, and a webhook that writes new signups in real time. The trial CRM, the Excel exports, and the email-marketing contact list collapse into one database the team queries directly. Marketing and support finally see the same number.
A 25-employee e-commerce brand
8,200 customers consolidated in 2 weeks
The brand describes how a customer differs from an order — household, order history, lifetime value, last purchase channel. Exepad publishes a database with relational links between customers and orders, search across both, and tag-based segments for campaigns. The export from a per-seat CRM, the support-tool contacts, and a loyalty platform spreadsheet merge into one database that every team can read from.
A regional nonprofit
3,500 supporters, 0 per-record fees
The nonprofit describes a supporter record — donor status, last gift, communication preferences, volunteer interests. Exepad publishes a database the team can search, segment, and export without paying per record. The donor-management SaaS contract — priced per contact and renewed annually — is no longer worth the budget, because the same record now lives in an app the nonprofit fully owns.
How it works
Four steps. No technical knowledge required.
Describe
Tell Exepad what a customer is in your business — the fields, the relationships, the segments. The convert engine turns the description into a no-code database app.
Configure
Refine the schema, validation rules, and views through prompts. Exepad models customers, orders, tags, and history in one relational database.
Publish
One click ships the database app to the global edge with SSL, Lighthouse 95+ performance, and structured markup so any public views are search-ready.
Invite
Point your custom domain at the app and invite teammates with role-based access. New-signup confirmation emails fire automatically from day one.
Who builds this
Common audiences and the job each one is trying to get done.
Bootstrapped SaaS or product company
A customer record that joins billing, usage, and lifecycle data — without paying a per-seat CRM tax just to see who your top accounts are.
E-commerce or DTC brand
Customers linked to orders, lifetime value calculated on the fly, segments for campaigns, and exports for the email platform — all from one database you own.
Nonprofit or membership organization
Supporter records with donation history, communication preferences, and volunteer interests — without paying donor-management SaaS by the contact.
B2B services firm
Account-and-contact hierarchy, custom fields for industry and deal size, and a database the partner team and operations team can both query directly.
Local business with a loyalty program
Customer records linked to visits, points, and last contact date — replacing a loyalty SaaS subscription with a database that costs the same flat fee.
Marketplace or community platform
Two-sided customer database for buyers and sellers, with role tags, verification status, and an API other Exepad apps can read from.
Metrics that matter
What to measure once it's live — the numbers that tell you it's working.
Customer count accuracy
Whether two team members querying the database get the same number. With one source of truth the answer is always yes — even at the end of the quarter.
Time-to-segment
Seconds from defining a segment to seeing the matching customers. A live database with indexed fields returns this in under a second at typical SMB volumes.
Data-portability rate
Share of customer fields you can export without paying extra. On Exepad this is always 100% — every field is a CSV or API call away.
Time-to-onboard a new tool
Hours to connect a new analytics or marketing tool to your customer data. With REST and MCP endpoints built in, this drops from days to one afternoon.
Common mistakes
What goes wrong most often — and the fix that turns the mistake into a working result.
Mistake
Storing customer data inside a marketing tool because that is where you first needed it.
Fix
The database belongs in a database. Marketing tools are downstream consumers — let them read from the source, not own it.
Mistake
Designing the schema around what a vendor's CRM expects.
Fix
Describe the fields your business actually uses. Exepad builds the database around your reality, not a generic pipeline template.
Mistake
Paying per record for a contact list that grows whether the contacts are active or not.
Fix
Use a flat-priced database and add a last-active field. Inactive contacts cost nothing extra and are easy to archive.
Mistake
Letting Excel exports be the only way to share customer data with another team.
Fix
Expose a read-only view or an API endpoint. Exports go stale within a day; a live view never does.
Mistake
Treating the database as set-and-forget and never reviewing field hygiene.
Fix
Schedule a monthly review of stale fields, duplicate records, and empty segments. The database is only as trustworthy as the last cleanup.
What replaces what
The stack collapses into one product.
One subscription. Eight production components.
Everything you need in the plan. No add-ons, no separate vendor invoices.
Database
Forms
File storage
Hosting
SSL
Visitor analytics
Custom domain
Frequently asked
How much does this cost compared to a per-record CRM?+
Per-record pricing punishes growth — every new signup raises the bill. Exepad is one flat monthly subscription that includes the database plus forms, file storage, transactional email, custom domain, and hosting. For a database of 5,000–50,000 customers it is usually a fraction of the per-record cost of a hosted CRM.
Can I really own the database, or is it locked in?+
You own it. Every field, every record, and every relationship is written to your relational database with REST and MCP access. You can export the whole thing to CSV anytime, query it directly, or feed it into other Exepad apps. There is no proprietary format that needs scraping to leave.
Do I need to know SQL or model a schema?+
No. You describe what a customer is in plain language — the fields, the relationships, the segments — and Exepad models the database, the forms, and the views. The schema is editable later through more prompts, and advanced users can still drop into raw queries through the API when needed.
Can I capture signups directly into the database with a form?+
Yes. Exepad ships a forms feature that writes straight to the database, with validation, custom fields, and confirmation emails included. You can embed the form on any page, host it under your own domain, and capture new customers without a third-party form service paying you to use their database instead.
Can other apps query the customer database?+
Yes. Every Exepad database exposes a REST endpoint and an MCP endpoint. Marketing tools, analytics dashboards, AI agents, and other Exepad apps can read or write through them with role-scoped tokens. Your customer database becomes the single source other systems point at, instead of holding their own copy.
What happens to my data if I leave Exepad?+
You export it. Every record and field exports to CSV, and the schema is documented as plain text you can read. There is no contractual lock-in — your customer list is yours the day you start and the day you leave, with the same one-click export available either way.
Will search engines or ChatGPT find database-backed pages?+
Yes, for any view you publish publicly. Public-facing pages — a customer directory, a member roster, a case-study database — ship Lighthouse 95+, structured schema, and direct-answer passages so search and AI assistants like ChatGPT or Perplexity can surface them when someone asks about your category.
Every Exepad customer database runs on a global edge network with 99.9% uptime, automatic SSL, daily backups, Lighthouse 95+ performance, and one-click CSV exports on every record.
Keep exploring
Start with one prompt
Describe the app you need. Exepad publishes a full-stack version with hosting, database, email, and analytics built in.
Describe your app →