Account
The organisation, contacts, owner, websites and every linked engagement.
CRM & Engagement
A signed deal should not erase the story that created it.
The moment an opportunity is marked won, most systems quietly discard everything that made it winnable: the thread where the client explained the real constraint, the objection that shaped the scope and the version of the offer that was signed.
In Genedar the sale does not disappear when delivery starts. The differentiator is not the pipeline. It is the continuity between sales, delivery, evidence and billing.
One relationship, four states
Lead
The inquiry, qualification state and source conversation.
Opportunity
The commercial number, stakeholders, scope, offer and decision.
Project
The won promise with an owner, team, work, documents, hours and evidence.
The timeline is the product
Notes, emails, meetings and field changes land on the same timeline. Archived mail and attachments are filed into the record’s SharePoint folder, so the evidence lives with the relationship rather than in a personal mailbox.
Offers and contracts stay attached through delivery. When the project lead asks what was promised, the answer is the document on the record — in the version that was sent.
Follow-up that comes from the record
Reach
- Marketing lists
- Governed inbox
- Global record search
Attention
- Stale accounts
- Dormant opportunities
- Named follow-up owner
- Duplicate detection with human-confirmed merge
Handover
- Won opportunity becomes the project
- Stakeholders carry over
- Commercial number survives
- Closing a deal closes its open tasks
Intake
An incoming request should arrive as a record, not as a task to type one
Forward a mail to a dedicated intake address and it becomes the record it was always going to become, while you were doing something else.
Everything an inquiry costs you before anybody has decided anything is typing: a lead somebody opens, fields somebody copies out of a mail, a thread somebody remembers to attach. Genedar does that part on arrival. The forwarded mail is read, its frame data extracted, matched to the account it belongs to where the match is unambiguous, and filed as a record with the original mail already on its timeline.
What is left is the decision, and the Inbox is the single place that shows what is waiting for one: mail to file, staffing requests nobody has taken, project requests still to route. A row leaves on its own the moment its record moves on, so there is no read flag to tick and nothing waits in two places at once.
One Inbox, three feeds
- Mail waiting to be filed, staffing requests nobody has touched, project requests still to route
- Rows leave on their own when their record moves on, so there is no read flag to tick
- You see only the feeds your permissions cover, and the sidebar count matches the list
Staffing requests rate themselves
- Role, start, duration, location and must-haves extracted onto the lead
- A Strong, Near or Weak reading with reasoning per must-have, naming the consultant and the evidence
- A reply to the agency and a briefing for the consultant, as drafts you edit and send from the timeline
Project requests open the deal
- The account is resolved from the sender's contact record, then from their mail domain, and never from a guess
- An unambiguous answer opens the opportunity and mints the project number; anything unclear waits in the Inbox to be filed
- The request mail lands on the new opportunity's timeline, so the deal starts with its own evidence
Triage that asks how to win, not whether to bother
A request that reached your mailbox has already been judged: a colleague looked at it and forwarded it, which is the decision. So the automatic triage does not grade the opportunity. It produces a win plan: the themes to lead with, how well the people you can offer today cover each must-have, the evidence behind that reading, and concrete options for closing a gap rather than a reason to walk away.
A skill that is plausible from comparable technology or industry context but missing from a profile is marked as a probable CV gap. That is an argument for putting the person forward, and a prompt to fix the profile.
Risks are named together with their mitigation, and a thin request produces clarifying questions you can forward as they are. The win plan is filed as a commercial-visibility note, so the consultant being proposed can see the deal and never the plan for them.
The intake also confirms back to the colleague who forwarded the mail, and only to them. An outside sender never receives a reply, so the mailbox gives nothing away.
Nothing arrives without somebody owing an answer
A request nobody answered is the one failure a customer actually notices, and it is never a decision. It is a mail that stopped being anybody's.
Every intake mail opens a reply task with an eight hour target and a twenty four hour hard limit, on the record the mail produced. A mail whose sender resolves to nobody still gets one, unassigned in its business unit, because the customer is owed a reply either way. The task closes itself when an outbound mail to the customer is filed, and the automatic confirmation to your own colleague never counts as that reply.
Answering the request is a first-class act too, not an export. Ask the assistant to rewrite a draft and it rewrites that draft in place, so there is one current version rather than a stack. Ask it for a consultant profile as a PDF and it returns one, anonymised or whitelabelled, permission-checked and audit-logged like the in-app dialog. The staffing reply offers those profiles as attachments per proposed person, and what you sent is filed back on the lead.
Bring one account, one open opportunity and one request mail.
We will follow the opportunity forward into the project, hours and invoice, and backward into the thread that started it. Then we will forward the mail to an intake address and watch it become a record.