A fake company generator produces complete, plausible-looking business records — name, industry, registration number, website, and a contact — for populating demo accounts and seeding test CRM data. Everything is fabricated, so you can build realistic B2B fixtures without referencing any real organisation.
How it works
Each company record is assembled from word lists and simple rules:
- A name is built from a random root word, an optional descriptor, and an industry-flavoured word, then closed with a legal suffix such as
Ltd,Inc,GmbH, orLLC. - An industry is drawn from a list (Software, Logistics, Healthcare, and so on).
- A registration number is generated to a plausible length and format.
- A website and contact email are derived from a slugified version of the name on safe example domains, giving you consistent, fictional contact details.
What each field contains
| Field | Format | Example |
|---|---|---|
| Company name | Root + descriptor + suffix | Northbridge Analytics Ltd |
| Industry | Category label | Logistics, SaaS, Healthcare |
| Registration number | 8-digit UK-style format | 08472953 |
| Website | Slugified name on example domain | northbridge-analytics.example.com |
| Contact email | firstname@domain format | [email protected] |
Practical uses for fake company data
CRM demos. Sales teams demonstrating Salesforce, HubSpot, Pipedrive or any B2B CRM need a populated pipeline to show filters, deal stages, and contact views. Fake company records let them run a live demo without exposing real client data.
B2B checkout and invoice testing. Many SaaS products bill companies rather than individuals, requiring a company name, registration number, and VAT ID on the invoice. Fake company records let QA engineers exercise the billing flow without creating real accounts.
Data import and mapping tests. When building or testing a CSV import feature, you need rows with consistent field types. A batch of fake companies gives you a controlled, varied set where you can deliberately include edge cases — long names, special characters, industries that might not map cleanly.
Wireframes and pitch decks. Mockups look far more credible with plausible company names in the UI. “Northbridge Analytics Ltd” in a pipeline view is more convincing to stakeholders than “Company 1” or “ACME Corp.”
API integration testing. When testing a webhook or API integration that sends company data to a third party (accounting software, a shipping provider, a KYC service), fabricated records let you exercise the integration without sending real client details.
A note on registration numbers
The generated registration numbers follow a plausible format — eight digits for UK Companies House style — but are random integers, not verified against any registry. They will pass a basic format check (right length, all digits) but will fail any check-digit validation or live lookup. For testing registration number validation specifically, you may need to calculate a valid check digit manually or use a well-known test number from a sandbox environment.
- Copy the batch as tab-separated rows to paste straight into a spreadsheet or a CRM import tool.
- Re-run any time for a fresh, non-repeating set of demo companies; nothing leaves your browser.