Your data. Your systems. Your control.
Plain answers to the questions business owners actually ask before letting anyone near their inbox, their customer list, or their accounting software.
01 / THIS WEBSITE
Where your information goes when you use this site
Everything on instepops.com is listed below. There is nothing else.
| What you do | What happens | Who handles it |
| Send an inquiry or request a call | Your name, company, email and message are emailed to Matt. Nothing is stored on the site. | IONOS (email), Vercel (runs the form) |
| Talk to the AI advisor | Your messages are sent to Anthropic’s API to generate replies. The conversation stays in your browser tab and is shared with Matt only if you request an Opportunity Brief. | Anthropic (Claude), under its API terms, which by default do not use customer data to train models |
| Request an Opportunity Brief | The brief is emailed to you, and the conversation and brief are emailed to Matt so he can follow up. | Anthropic, IONOS, Vercel |
| Use the “See it work” demo | The message you paste is sent to Anthropic’s API to produce the result. The site does not keep the message or the result. | Anthropic, Vercel |
| Just browse | Page views are counted without cookies or personal identifiers. No marketing cookies, no ad trackers. | Vercel Web Analytics |
To have an inquiry or brief removed from Matt’s inbox, email matthew@instepops.com. Please don’t paste passwords, card numbers or confidential customer data anywhere on this site; the advisor and demo are built to ask you not to.
02 / DURING AN ENGAGEMENT
How we work inside your business
These are commitments, not aspirations. They go in the scope document for every project.
◎Your data stays in your accounts
We work inside tools you own, through user accounts and API keys you create and can revoke at any time. Customer lists, pricing and financials are not copied to personal devices or outside systems. Where a workflow needs AI, we use business API services whose terms do not train on your data, and we tell you which ones.
✳You own everything we build
Workflows, prompts, documentation, integrations and the accounts they run in belong to you from day one. Handover is part of the work: a plain-language runbook, the list of what can be changed safely, and who to call. If we part ways, it keeps running, or you switch it off. There is no lock-in and nothing proprietary you can’t take with you.
⇄People approve what matters
Prices, orders, payments and customer commitments get a human approval step by default. During pilots, nothing goes to a customer without a person seeing it. Anything unclear, duplicated or outside the agreed rules is routed to a person rather than guessed. Only after measured results, and only if you decide to, do routine steps move toward automatic.
↗If something breaks
Every workflow has an off switch, and the fallback is the process you have today. Errors are logged and queued for a person; nothing is silently dropped. We set up alerts for failures and vendor outages, and the runbook says what to do before you call us. Changes to live workflows are tested on sample data first.
03 / WHAT WE DON’T DO
Lines we don’t cross
- We don’t scrape personal data, use bought contact lists, or set up bulk messaging to people who never asked to hear from you.
- We don’t let an automation quote a price, place an order, or move money without a person approving it, unless you have measured it working and chosen to change that.
- We don’t hide costs. Software, AI usage and vendor fees are listed up front and billed at cost.
- We don’t sell, share or reuse your data, and we don’t use one client’s information to help another.
- We don’t recommend a build when a process change or a feature you already own would do the job. The written assessment says so when that’s the case.
04 / FOR ANY VENDOR
Questions worth asking anyone who offers you “AI automation”
Including us. If the answers are vague, keep your wallet closed.
About your data
- Which services will see my customer data, and under what terms?
- Who holds the accounts and API keys, and can I revoke them?
- Is anything used to train AI models?
About control
- What can this thing do without a person approving it?
- How do I turn it off, and what happens to work in progress?
- What happens when it is unsure?
About results
- What will we measure before and after, and who measures it?
- What does the pilot cost, fixed, and what is excluded?
- What does it cost to run each month after launch?
About the exit
- If we stop working together, what keeps running?
- What documentation do we get, and can someone else maintain it?
- What has this vendor actually built and measured before?