Design proposal
What your client portal could look like
One place to book your meetings, see where your engagement stands, and read at a glance how many signups, conversations and closed deals came out of it.
Example
The dashboard
The three numbers that matter, right as you walk in: how many people signed up, how many conversations came out of that, and how many of those turned into a signed deal.
-
Example
24
Signups
this month
-
Example
11
Conversations held
this month
-
Example
3
Deals closed
this month
Every figure above is an example value. In a real portal these numbers come from the database behind your own account, can be filtered by period, and show you where people dropped off.
Recent activity
- Signup through the website
- Sales Diagnose scheduled
- Conversation held, proposal requested
- Proposal signed
Calendar & meetings
In a portal like this you would book a meeting without emailing back and forth: you pick a slot that is open, and the confirmation would run through website@dcraftofsales.com.
Example schedule
-
Monday
09:0011:3015:00
-
Tuesday
10:0014:00
-
Wednesday
09:3013:0016:30
-
Thursday
11:00
-
Friday
09:0012:0015:30
The times above are examples and cannot be booked — there is no calendar behind this page. Want a meeting now? That works fine, through the button below or by phone.
Goes straight to website@dcraftofsales.com. Prefer to move right away? Call or WhatsApp us — that is the fastest route.
What else would be in it
A portal is only worth having if you get something out of it every week. These are the parts that make that true.
-
Calendar and meetings
Open slots, booking in two clicks, an automatic confirmation and a reminder up front.
-
Progress of your engagement
What has been delivered, what we are working on now, and what is waiting on you.
-
Documents
Proposal, order confirmation, data processing agreement and reports, all in one place.
-
Figures
Signups, conversations held and deals closed from your own pipeline, by period.
-
Our tools
The Dcraft Of Sales AI tools from inside your own account, with your earlier results within reach.
-
Direct contact
One button to the people working on your engagement right now.
What it takes to actually build this
This website is static: pre-built pages, no database and no sessions. A portal is therefore not one more page — it is an application. In concrete terms, that means the following.
- Accounts
- Every client gets their own account, with the option to let colleagues in and to decide per role who sees what.
- Authentication
- Sign-in with a password or a login link, sessions that expire, and two-factor authentication for accounts that see sensitive data.
- Database
- Signups, conversations, meetings, documents and statuses have to live somewhere — with backups and a restore procedure that has been tested.
- Authorization
- Every client sees strictly their own data. That has to be enforced on the server, not in the browser.
- Integrations
- The calendar has to stay in sync with Google Calendar, and confirmations and reminders have to go out automatically.
- Server environment
- From static hosting to a running application with a database, logging, monitoring and maintenance that keeps going.
- Privacy and agreements
- Personal data in a portal calls for a data processing agreement, documented retention periods and a working procedure for access and deletion requests.
In short: this is a separate track alongside the website, with its own planning and its own maintenance phase. What you see above is the shape — not the build.
Do you actually want this?
Then we work out together what your portal has to do, what it deliberately does not have to do, and what it takes to build it. That conversation starts with the Sales Diagnose.