CRM
Demo requests
People who asked for a demo and confirmed their email · approve to build their demo
2 awaiting you
✅
How a demo gets here: someone fills the form on the site → we email them a verify link →
they click it (so the email is real) → the request lands here. You press Approve & build demo,
and the isolated demo space, username and password are created and emailed to them automatically.
Nothing is built for an unverified email.
Handling of new requests
How the site treats a new demo request before it reaches you.
Fleet health
Built from last night's reports · 41 installations · nothing here is customer data
🎯
This page should be boring. It only shows installations that broke one of your rules.
Everything else stayed quiet last night and is not worth your morning.
Installations
41
39 reported last night
Needs you
2
Down from 4 last week
Backups ok
40 / 41
Last 7 nights
On latest version
34 / 41
2.3.1 · 7 behind
Needs you
Sorted by how bad it is, not by when it arrived.
| Company | What | Whose job | Since |
|---|
Sorted itself out
No action needed. Here so you know the machinery is working.
| Company | What happened | When |
|---|
Bugs
One row per fault, however many companies hit it · grouped by fingerprint
🧮
19 errors across 6 companies is one row, not nineteen. Every error carries a fingerprint —
a signature of the fault itself — so the same fault in different companies stacks up into a single
line with a count. That count is what tells you what to fix first.
| Fault | Where | Companies | Times | Version | Status |
|---|
Support inbox
Messages customers sent from inside their software · you reply, and it lands back in their app
2 waiting for you
📨
This is the one channel that reaches you from a customer's server. They write from
Settings → Talk to Projexin support; it arrives here with their version and any error code.
You only ever see what they chose to send — never their projects, files or messages.
New
0
No reply yet — start here
Open
0
You replied · being worked on
Waiting on customer
0
Their turn to answer
Resolved · 7 days
4
Closed this week
🗄️
Every message, every reply — kept for good. Nothing here is ever deleted, not even after a case is
resolved. It is your permanent, dated record of what was said to whom, safe to lean on later. It is backed up
every night alongside the rest of the console, and you can pull a full report of it any time with
Export report.
How to work a message — the same four moves every time
Nothing to memorise. Every message is one of these.
① A question (“how do I…?”)Type the answer, press Send reply, then Resolve. Done.
② A real fault (has an error code / “it broke”)Reply “we’re on it”, press Send to Bugs — it becomes a tracked bug. Fix it, ship an update in Releases, come back and Resolve.
③ You need more from themAsk your question, press Send reply — status becomes Waiting on customer until they answer.
④ Not your problem to solve (their server / their staff)Explain kindly, point them the right way, and Resolve.
⏱️
One rule keeps this calm: reply to every new message within one working day, even if the reply is just “got it, looking into this now.” A customer who knows they’ve been heard waits happily; silence is what turns a small fault into an angry email.
Message a customer
Pick who to reach, write a short note — it appears inside their software, for the main admin only
📢
This is how you reach a customer without email. Your note travels down the same
secure check-in the software already makes to us — nothing new is opened, no address is needed.
It shows up as a calm banner at the top of the main admin's screen the next time they open Projexin
(so, the start of their working day). Only the company's main admin sees it — not their staff.
You will see a ✓ here once they have read it.
Write a new message
Keep it short and plain. This is best for friendly heads-ups — “an update is coming”, “thank you”, “planned maintenance Saturday”. For a fault a customer reported, use the Support inbox instead.
0 characters
👀
Preview — this is roughly what their main admin will see at the top of their screen:
📢
A note from Projexin
Your message will appear here…
Sent ✓
Messages you have sent
Every message is kept for good and shows who has read it. Use the Excel / PDF buttons at the top to pull a full record.
Customers
41 paying · 3 in their first month
Monthly recurring
C$2,144
41 companies
Renewals in 30 days
6
C$318 at stake
Overdue payment
1
Northline · 12 days
Left this year
2
Both moved to a bigger system
🎚️
The “Update ring” column is where you set who gets updates early. Change it right here, any time.
Ring 2 = your volunteers, they get a new version first; Ring 3 = everyone else, they get it last,
once it is proven. (Ring 1 is your own demo server, not a customer.) A customer keeps its ring until you change it.
| Company | Plan | Version | Update ring | Server | Health | Renews | Payment |
|---|
Sales pipeline
Every enquiry, from first contact to installed
What to automate first
Everything here is possible. The order matters more than the list.
✅ Do now — it is easy and it never sleepsLicence key on payment · portal account · welcome message
✅ Do now — it saves you from forgettingRenewal reminders · trial expiry · overdue payment chase
⏳ Wait until 20 customersAutomatic server provisioning
🤝 Keep human on purposeThe install call and the handover of keys — that is where the relationship gets built
Trials
3-day accounts on your demo server · 4 running, 12 finished this month
Issued this month
16
demo logins sent
Signed in
13
81% · the rest never came
Running now
4
still inside their 3 days
Entered real data
7
built a project of their own
🤝
Overall behaviour only — never what they typed. We look at the shape of a trial: how long they spent,
which days they came back, and how far into the software they got. That is all the follow-up report needs. We do
not read, monitor or judge the content a prospect enters — the demo is theirs to explore freely.
🧹
Keep the demo server tidy. Every demo is a separate space that takes room. Open any trial below and
use Delete this workspace to remove one you no longer need — its register entry stays, only the space is freed.
| Who | Trade · town | Workspace | Day | Visits | Time | Data in | Verdict |
|---|
Follow up
Who to call today, in order · scored from what they did, not when they signed up
🎯
Work it from the top. The list is ranked, so the person most likely to buy is the
first row. Someone who entered real data and came back more than once outranks someone who
signed up a week earlier and never returned.
How the ranking works
No black box — four signals, in plain order of weight.
① Invited a colleague to the trialThe strongest signal there is — they are picturing their office on it
② Entered real data of their ownA job with actual costs means they tested it against real work
③ Came back more than onceOne visit is curiosity; three is consideration
④ Reached Job CostingThe screen most buyers say decided it
Already followed up
What happened on the calls you have made.
| Who | Trade · town | Outcome | Note |
|---|
Demo register
Every demo ever issued · never deleted · 68 entries since March
📖
The space expires. The record does not. A demo login stops working after three days and
the sample data is cleared out ninety days later — but the entry below stays for good. When
somebody rings in November about the demo they took in March, you open their line and carry on
from where it stopped instead of starting again.
Demos issued
68
since March
Became customers
19
28 in every 100
Never signed in
11
16% — asked, then never came
Still open
6
4 running · 2 worth chasing
Which channel actually sells
Not which one sends the most people — which one sends the ones who buy.
After fifty entries this table is the most valuable thing in the console.
| Where they came from | Demos | Bought | Rate |
|---|
💡
Look at the rates before you spend another dollar on advertising. A channel that sends
thirty people and sells to one is costing you money that the channel sending six and
selling to three would turn into customers.
| Issued | Who | Trade · town | Came from | Used it | Outcome | Note |
|---|
Releases
Nothing reaches everybody on the first day
Version spread across the fleet
Anyone more than two versions behind gets a nudge. Anyone four behind gets a phone call.
The two rules that keep going back possible
1 · Never delete a database column in the same release that stops using it
Delete it one release later
2 · Test the long jump
A server switched off for three months goes 2.1 → 2.4 in one night
Website
Manage projexin.com yourself — the menu, the wording and the pictures. No code, nobody to wait on.
Live · projexin.com
🌐
Your site is edited on the site itself — not from a form in here. You open projexin.com, press
✎ Edit this site at the top, and every part of every page can be changed by clicking it.
Nothing you change there can ever reach a customer's installation or their data.
Three things you can change — all from the live site
No code, nobody to wait on. You press Publish when you're happy and it goes live on projexin.com.
Wording
Click & type
Any text on any page — the headline, the prices, a button, a whole paragraph. Everything is editable.
Pictures
Hover & replace
Swap any picture for one from your own computer, right where it sits.
Menu & pages
Show · hide · reorder
Add, rename, hide or reorder the menu items from the side panel.
Open your site in edit mode
This opens projexin.com straight into edit mode, where you can change any text,
replace any picture, and reorder the menu — then press Publish.
Terms & policy
The one place your site's legal documents live · edit, publish, and notify customers of changes
📜
Whatever you write here is what the site shows. Each document is versioned and dated, so you always
have a record of exactly what was in force and when. When you change one, publish it and then send the
customers a formal notice from the next tab.
📣
Formal notice, so nobody can say they were not told. The list below is built automatically from
your customers' verified billing emails. Pick what changed, review the message, and one click sends a dated,
formatted notice with a link to read the new terms. Every send is logged.
Compose the change notice
Edit anything before it goes out. One email, to every customer on the list below.
Keep the line [read link] where you want the “Read our updated Terms & Policies” button to appear (it links to projexin.com/legal).
Customers on the notice list
Built automatically · 0 verified billing emails
| Company | Status |
|---|
Notices sent — proof of delivery
The permanent record of every change notice: when, from where, the subject, and the exact list of who it went to. Export it any time as proof that everyone was told.
| Date | From | Subject | Version | Recipients |
|---|
Team & access
Who can use this console, and how much of it · add support people without giving away everything
👤
This is the console's own team — not your customers, and not their software users. Add someone here
when you need help answering customers or watching the fleet. You choose exactly how much each person can touch.
| Person | Role | Can open | Status |
|---|
The four access levels
Pick the smallest one that lets a person do their job. You can change it any time.
👑 Owner (you)Everything, including this Team page, Releases and billing. Usually just you.
🎧 Support agentSupport inbox and Bugs only. Answers customers and logs faults — cannot see money, customers list or releases.
📊 SalesSales pipeline, Trials, Demo register, Follow up. The commercial side — no bugs, no releases.
👁 Read-onlyCan look at Fleet health and reports, change nothing. For a bookkeeper or an advisor.
🔑
Every teammate signs in with their own email and password and two-step sign-in, and everything they do here
is recorded — who replied to which customer, who shipped which release. Nothing is anonymous.