Synthetic Data for CRM

Describe the sales motion, for example 1,000 accounts and 12 reps over two years, and Misata Studio builds accounts, sales reps, opportunities that move through pipeline stages, and the activities around them. Each opportunity's rep is its account's rep, deals move through the stages in order, and each rep's won deals and quota attainment are worked out from the opportunities themselves. Export it as Salesforce's standard objects or HubSpot's, with a script that loads them into your org or portal.

Updated 2026-09-24.

You would write

A B2B sales team with 12 reps, 1,000 accounts, opportunities through the pipeline stages and sales activity over two years.

Studio builds this on one of its tested archetypes: the mechanics below are fixed and verified, and what the business sells, the names and the wording are written for yours.

Start from this

What Studio builds

accountsCustomers and prospects, each a business of its own country: industry, headcount, legal name, domain, address and phone
contactsThe buying committee at each company, by department and seniority, met before any deal names them
sales_repsThe team, with territories
opportunitiesWon, lost and open deals with stages, amounts, close dates and how often they slipped, lead source, loss reason and competitor; the rep comes from the account
sales_activityCalls, emails, demos and meetings tied to real opportunities, with whom and what came of it

What holds, and how you know

These are checked on the finished data, not assumed. Each dataset comes with a certificate listing what you asked for and whether it was met. How we verify.

  • An opportunity's rep is always its account's rep
  • Deals pass through the stages in order, with a date for each stage reached
  • Each rep's won deals, won amount and quota attainment are worked out from their opportunities
  • Salesforce and HubSpot exports name every parent by an external id and load parents first
  • Every foreign key points at a row that exists, checked on the finished data
  • Every count, total, rate, share and date window you state is applied exactly, or listed as not applied
  • A certificate lists each requirement and whether the data meets it

Have a schema, specialised rules or a large volume and would rather hand it off? Ask us to build it for you.

Frequently asked

Do I need real CRM data to generate this?
No. Misata Studio builds the dataset from a description, a schema you draw, or a structure you import (SQL DDL, DBML or a CSV header). No real records are uploaded, copied or learned from, so there is nothing to anonymise.
Can real CRM records end up in the generated data?
No. Nothing is learned from real records, so no real person, customer or account can appear in the output. A model writes names, places and wording, and Studio may research public facts on the web (you can turn research off). It never asks for your data.
Can I control the numbers, like rates and totals?
Yes. State a total, a monthly curve, a share or a rate in plain words, or draw the curve, and Studio applies it exactly. The certificate lists each figure and whether it was met. If a figure cannot be met, Studio says so instead of changing it.
Can I use my own schema?
Yes. Paste SQL DDL or DBML, import a CSV structure, or draw the tables on the canvas. A schema you give is followed exactly, and any difference is reported.
Which formats can I export?
CSV, Excel, Parquet, JSON Lines, SQL for Postgres, MySQL, SQL Server, Oracle, BigQuery, Snowflake and ClickHouse, SQLite, DuckDB, dbt seeds, Prisma, DBML, TypeScript, JSON Schema, a data dictionary, Salesforce and HubSpot objects with a loader script, and more.