Sales
Picture Muster GmbH, a 30-person German SME where the founder still runs sales alongside three other jobs. Business-Gym gives that founder a triaged lead queue, one real write into the CRM, and a pipeline board that can be read in ten seconds — it does not give them a sales autopilot.
Exactly one sales action reaches your CRM today: creating a lead, and it runs only after a person approves that specific item. Everything else on this page is either a read view or a proposal waiting for you. This page walks through a realistic week and marks which is which.
What does a sales week actually look like?
Section titled “What does a sales week actually look like?”The rhythm is a short daily pass over the inbound queue plus a longer look at the board when you want to know where the quarter stands — roughly the sales attention a founder with three other jobs can spare.
| When | What happens | Who acts |
|---|---|---|
| Through the day | Leads arrive from your mailboxes, LinkedIn and Meta, and land in the triage queue classified and routed | Nobody — reading and sorting only |
| When you work the queue | You press Create CRM lead on the real ones; each press stages a pending approval | You, one message at a time |
| In the approval queue | You approve, and the lead is created in Dynamics — or linked to a record already there | You, at the gate |
| Every two hours | Open Dynamics opportunities refresh into the pipeline board as read-only projections | Nobody — sync only |
| Any day | You read Pipeline for the shape and Sales analytics for the numbers | You, reading |
| When a deal moves | You pick a new stage on the card, which stages a proposal rather than moving the deal | You, then a second yes |
Nothing in that week runs to completion on its own. The gate in the middle is the same hard floor that governs every external effect in the platform, and it does not move as autonomy rises.
How does a lead in your inbox become a record in Dynamics?
Section titled “How does a lead in your inbox become a record in Dynamics?”You press Create CRM lead on a triaged message, and that stages a pending approval — at that moment nothing has reached your CRM at all.
The button sits on the message in the inbound triage cockpit, alongside the other one-click verbs. Any member with read access can stage one; the screen then confirms “CRM lead staged — review in Approvals.” and the item appears in the queue labelled Inbound · CRM lead.
Staging is reads only, and it does one useful read first. When Dynamics is connected, it looks for a contact or lead that already matches the sender, so the staged card offers linking to the existing record instead of creating a duplicate.
Approving is where something actually happens, and it takes one of two shapes:
- Link — the staged match is reused. The existing Dynamics record is adopted and no CRM write happens at all.
- Create — one lead is written, carrying the subject and sender name, plus company, email, country, phone, job title and source when the message arrived with those fields structured.
Either way the triage row is then stamped with the record it resolved to, so the message and its whole thread show which CRM record they belong to.
What does Business-Gym read from your CRM?
Section titled “What does Business-Gym read from your CRM?”It reads the customer, contact, lead and opportunity side of Dynamics, and it never becomes the master of those records — what you see in Business-Gym is a projection of what lives in your CRM.
On a customer’s page, a Live CRM record panel with a Deep-dive in CRM button reads the live record on demand and lists the related Opportunities, Orders and Activities. It carries an honest status: Live, Not connected, Not in CRM or CRM unreachable. When it cannot read, it says “Could not read the CRM. Showing nothing rather than stale data.” rather than showing you yesterday’s numbers.
Open opportunities refresh on their own roughly every two hours, bounded so one sync can never turn into an unbounded write loop. That sync runs only when your opportunity records are bound to Dynamics as their system of record — a per-record-type choice on the CRM System of Record card under Integrations, which is owner or admin only.
Where do you see the pipeline?
Section titled “Where do you see the pipeline?”Two pages under Sales in the left navigation carry the whole picture: Pipeline, a board of your deals grouped by stage, and Sales analytics, the numbers computed over those same deals.
The board lays out one column per stage in the order lead → qualified → proposal → negotiation → won → lost, showing every stage even when it is empty so you always see the full shape. Stages of your own appear after the standard six. A row above the board reads like “12 deals · €480,000” with the source mix beside it — how many deals are native to Business-Gym and how many came from your CRM.
Each card shows the deal name, its value, the chance of winning, the owner, the close date, a Native or CRM badge, and — on CRM-sourced deals whose connection address is configured — an “Open in … ↗” deep link back to the original record.
Sales analytics turns the same deals into four figures — Open pipeline, Weighted forecast, Win rate and Avg. cycle — plus a funnel by stage and roll-ups by head and by legal entity.
What happens when you propose moving a deal?
Section titled “What happens when you propose moving a deal?”Picking a target stage in the Move to… picker on a card stages a proposal and changes nothing — not the board, and not your CRM.
The control then reads “Proposed · pending approval ↗”, and the card gains a warning badge such as “Pending approval → negotiation” that links straight to your queue. Picking the stage the deal is already on does nothing at all. Proposing a move is owner or admin only.
What happens when you approve a change to a customer record?
Section titled “What happens when you approve a change to a customer record?”The approval now records what actually happened, which is precisely the part that was broken until recently and is worth understanding before you rely on it.
Previously, approving a customer field write-back showed only a green ”✓ Approved” while nothing ran and nothing was recorded. That is the worst failure shape in the whole platform: the human half of the loop completes, you see success, and the machine half silently never happens.
Now every path writes a truthful outcome line beneath the decision in the approval history:
- ✅ written — the field reached the connected CRM.
- ⚠️ not written, with the reason stated — either the live write path is switched off for this workspace, or Dynamics is not connected.
- ❌ failed, with the error from the CRM attached.
Re-running never double-writes, either: an approval already recorded as executed is not written a second time.
There is also no button in the app for proposing a customer field change today. The Live CRM record panel on a customer is read-only; the proposal is staged through the API and is owner or admin only.
How do LinkedIn conversations reach your sales queue?
Section titled “How do LinkedIn conversations reach your sales queue?”LinkedIn arrives through the BG UI Operator, a desktop application running on a PC you control, working inside your own logged-in LinkedIn session rather than through an API.
Registered operators are managed under Admin ▸ Operators, and each LinkedIn row on the Channels page shows an operator chip — operator live, operator offline or operator not connected. When that machine is off, nothing new arrives and the channel says so instead of presenting an empty inbox as “all caught up”.
Once a conversation is in, it gets the same treatment as an email: classified, routed, and eligible for the same Create CRM lead verb. A lead raised from LinkedIn cites its conversation thread as its source rather than a mailbox, so you can trace the record back to the message it came from.
A LinkedIn reply never leaves on its own. The operator is read-only for messages; where the reply path is enabled at all, it types your approved draft into the compose box and stops — you click Send yourself. Auto-drafting a reply for a confident LinkedIn lead is switched off by default. More on the channel mechanics is in email and channels.
What is not built yet?
Section titled “What is not built yet?”These are real gaps today rather than roadmap language, listed here because finding them in the product costs you far more than reading them now.
There is no create-a-deal screen. The pipeline board is a read view over synced and native deals; you cannot open a new opportunity from it.
The opportunity stage write-back is not wired. Approving a stage move records your decision and truthfully reports that the deal was not moved in the CRM.
The customer field write-back has no button and its live write is off by default, as described above.
Nothing learns from your sales decisions yet. Which leads you promote, which drafts you rewrite and which proposals you reject are all recorded, but none of it changes what gets proposed next week — the same gap described in how your team learns.
There is no native mobile app and no push notifications. Nothing taps you on the shoulder when a lead approval lands; you go and look, in the web app. Which roles can approve, and where, is covered in who can approve, and where.
To see the same propose-then-approve pattern in a different department, read finance; to set the targets this pipeline is meant to serve, use goals and OKRs.