Answers
FAQs
Understand how GREX works.
What it is
7What is GREX?
GREX is a growth operating system. We connect your marketing tools and knowledge, launch expert-built growth systems customised to your business, and test every activity against your North Star so you can see what's working.
Is GREX software or a service?
Both. You get the platform and the systems, plus a GTM engineer every week and channel experts on the systems you add. We call it service-as-software: built for you, run with you, owned by you.
How fast can we be live?
Your first system goes live within 14 days of kickoff. The How we work page shows the day-by-day plan.
What does it cost?
£3,000 a month for the core plan (platform plus your GTM engineer), plus £500 a month for each channel expert you add. There's a £3,000 launch fee, which comes back to you when we both hit the launch milestones. See Pricing.
Do we need to use Claude?
GREX works inside Claude today through MCP. It's headless, so it isn't tied to one model.
How is this different from giving ChatGPT access to our documents?
A chat assistant answers when you ask. GREX runs whether you ask or not.
The unit here is a process: a named piece of recurring work with a trigger, a written method, an owner and a record of every time it ran. That is what a chat window has no place to put. Ask an assistant to chase overdue invoices and you get a good answer once. Put it in GREX and it happens every Tuesday, and writes down what it did.
The knowledge is the other half. Your methods, your metrics, your tools and who owns what live in one model rather than in a prompt somebody pasted and then lost.
Do we have to replace Notion, Asana or HubSpot?
No, and we would rather you did not. GREX connects to the tools you already run and reads and writes through them.
What it adds is the layer above: one place that knows what work exists, who owns it, which tools it touches, and how it is doing. Keep your CRM as your CRM. The point is to stop the answer to "how does this actually get done here" living in four apps and three people's heads.
Your data and your IP
5Who owns the IP in the processes we build?
You do. Everything you put in is yours, and so is everything the system produces from it: your data, your process definitions, your documents, your history.
We own our software. Nothing you build inside GREX gives us any claim over your business or your ways of working, and that does not change if you leave. No licence back to us, no copy retained for our benefit.
Do you train models on our data?
No. Your workspace data is used to run your workspace, and for nothing else. We do not train models on it and we do not pool it across customers.
The model providers behind GREX operate under API terms that exclude training on submitted data. Retention and sub-processor detail is set out in our DPA, which we will send you before you sign anything.
How do we get our data out, and what do we actually get?
You do not have to ask. You get API access from day one and every object in your workspace has a read endpoint, so you can pull a full copy on your own schedule to your own storage. We will also generate a complete export bundle whenever you want one, and automatically on termination before anything is deleted.
What is in it: one JSON file containing everything, the same content split by type with metric history as CSV, and every process method as plain readable Markdown. That last part is the one that matters most. JSON, CSV and Markdown, with nothing that needs our software to open it.
Ask us for the sample export and we will send you the real thing to look at before you commit.
What are your exit terms if we want to leave?
Your systems, playbooks, data and experiment log are yours. We'll export them. We will put these in the contract:
- Export at any time during the term, at no charge.
- Up to 30 days of transition assistance on notice, extended if your migration needs longer.
- 7 days after termination to retrieve your data, then full deletion with written confirmation.
- No egress or switching charges, ever.
We would rather commit to this in writing than leave it to interpretation.
What happens to our data if GREX goes out of business?
Fair question to ask a young company, and a promise is the weakest possible answer to it.
The real protection is that you already hold the data. If you run a scheduled export against the API, a current copy sits on your own storage at all times, independent of us and independent of whether we are still here. We will set that up with you during onboarding rather than wait for you to worry about it.
If your legal team wants belt and braces on top, we are open to a source code escrow arrangement.
Something here not answered, or answered too thinly? Tell us and we will answer it properly, then put it on this page.