Your demo org
A real Expedify org, not a sandbox with pretend buttons — what is in it, how you get one, and the three ways people break one in the first week.
You cannot sell what you cannot show. So a partner is given an org of their own: a complete, working business with data in it, automations running, and a knowledge base that answers questions. Not a tour, not a video, not a shared login everybody is typing into at once. Yours.
It is a real org
This is the thing to understand before anything else. It is not a sandbox or a simulation. It is an ordinary Expedify organisation, created the same way a paying customer's is, and everything you do in it does what it would do in theirs. Workflows really run. Emails really send. The knowledge base really searches.
Which is what makes the course worth doing, and what makes the next section worth reading. Nothing here is pretend, including the consequences.
What is inside it
| In your org | |
|---|---|
| The business | Anvaya Finserv — a loan and protection advisory in Delhi NCR |
| Enquiries and people | 96 deals · 110 contacts · 8 companies |
| Automations | 19 workflows — 7 running, 12 drafts |
| Knowledge | 3 knowledge bases · 31 documents |
| What it sells | 5 products |
The business
- In your org
- Anvaya Finserv — a loan and protection advisory in Delhi NCR
Enquiries and people
- In your org
96 deals · 110 contacts · 8 companies
Automations
- In your org
19 workflows — 7 running, 12 drafts
Knowledge
- In your org
3 knowledge bases · 31 documents
What it sells
- In your org
5 products
Two of those numbers will look wrong on your first morning, and both are correct. Most of the workflows are drafts, and your execution log is empty. Both have reasons, and both are lessons later on.
- 7 drafts are waiting on a credential only a client can supply — a WhatsApp number, a telephony number, a calendar, an ad account. They are finished, not unfinished.
- 5 more are waiting on a decision — they would run today, and nobody has switched them on.
- Your execution log opens empty, because history does not travel when an org is created. The first thing you run will be the first thing in it, and that is deliberate — you will read your own run rather than somebody else's.
How you get one
A demo org is granted per partner, on request, rather than shared — so what you do in yours affects nobody else. Ask your partner contact for one; an administrator provisions it, adds you as a user, and sets it up with a credit allowance.
One thing to check on the day it arrives: that your org's integrations came with it. If they did not, one of the first workflows you will read — the lead intake in Capturing a lead from any other system — has no live URL to post to, and the exercise in that lesson cannot be done. It is a provisioning tick-box, and it is much easier to fix on day one than in week three.
It costs real money to run, and the tail is what bites
The org comes with a credit allowance, and a thorough session through this course costs a small fraction of it. That is not the risk. The risk is what happens while you are not watching.
| What | Roughly | Why it matters |
|---|---|---|
| A workflow step | 0.1 credits | Effectively free. Most of this org is these. |
| An AI call | ~0.4 credits | Small, and you make a lot of them. |
| A minute of voice | ~5.5 credits | About fifty times the cost of text, per minute of demo. |
A workflow step
- Roughly
0.1 credits- Why it matters
- Effectively free. Most of this org is these.
An AI call
- Roughly
~0.4 credits- Why it matters
- Small, and you make a lot of them.
A minute of voice
- Roughly
~5.5 credits- Why it matters
- About fifty times the cost of text, per minute of demo.
So: do not switch on anything that runs on a schedule. It is the single most likely way a demo org quietly empties. A workflow you activated on Tuesday and forgot about does not stop on Friday, and nobody is watching an org at three in the morning. This course will tell you twice more not to activate the morning sweep — this is why.
If you make a mess of it, ask for a reset
Most people who think they need more credits actually need a clean org. A reset puts it back exactly as it arrived, costs nothing, and takes minutes. If you have deleted half the enquiries, left three schedulers running and renamed a stage everything depended on — reset it and start the module again. That is a better instinct than carefully unpicking your own damage.
- Delete what you create. Every exercise in this course that makes something also tells you to remove it. Do that and a reset is never needed.
- Change one thing at a time. The lessons are built that way for a reason: when something moves, you know what moved it.
- Do not treat it as a client's org. It is yours to break. Breaking it here is the cheapest place you will ever do it.
Before you go on
- Log in to your demo org and confirm you can see a board with enquiries on it.
- Check integrations came with it.
- Open the workflow list and notice how many say draft. You are not missing anything.
- Do not switch anything on yet.
Next: The deals board and the seven stages — the board itself, and the seven columns that turn out to be load-bearing for six of the automations.
Related lessons
Base rates — what a piece of evidence is actually worth
A face-recognition system that is 99.9% accurate and almost entirely wrong, and a number that sent an innocent woman to prison. Both are the same arithmetic, and it is the arithmetic that decides what any piece of evidence is worth.
ReadConfirmation and survivorship — what you never looked for
Two questions about evidence you did not go looking for. One is a rule you have to discover, and one is a pattern in five famous people — and in both, the thing that would have told you the truth is the thing nobody checks.
ReadLoss aversion, sunk cost and regression — what it costs you
Four questions you answer about yourself rather than about a scenario, and your own answers are the finding. Then the pattern that makes praise look useless and criticism look like it works, whatever you actually do.
Read