Pipelines and stages
Stages mirror what genuinely happens: incoming request, qualification, site survey, quote, follow-up, order. A second pipeline for key accounts or public tenders when the decision route bears no resemblance to the rest.
Take a manufacturing firm of forty staff: quote requests land in three different mailboxes, follow-ups live in the heads of two salespeople, and the owner finds out a deal is lost on the day the customer signs elsewhere. Bitrix24 can sort that out, on one condition: the portal has to look like your trade, not like the demo template you meet at first login. So we begin by listening to how you sell, who decides what, and at which point files come to a halt. Configuration follows, and only where it earns its place.
We move one module at a time, in the order your teams need them. A portal stuffed with unused features always ends up bypassed by a shared spreadsheet.
Stages mirror what genuinely happens: incoming request, qualification, site survey, quote, follow-up, order. A second pipeline for key accounts or public tenders when the decision route bears no resemblance to the rest.
Mailboxes hosted on Microsoft 365, on Google Workspace or on plain IMAP, plus website forms and call-back requests, all reach the portal and get routed by a written rule rather than by whoever opens their inbox fastest.
Nothing but the fields someone works with afterwards. Every surplus mandatory box pushes a busy salesperson to type anything at all just to reach the next screen.
Dated tasks with a single owner, ready-made templates for jobs that repeat, a board view for people who think visually, and workload visible per person before anyone promises a deadline.
The quote leaves the portal, a won deal triggers the invoice in Sage, Cegid, EBP, Pennylane or Odoo through the API, and payment status returns to the record. Factur-X formatting and submission through your e-invoicing platform stay on the accounting side.
Directory, org chart, internal news, holiday requests routed for approval, procedures kept in one library. Worth most to teams split between office and home, who otherwise lose track of what was decided.
Which clients each role can see, who may export, how long a dormant contact stays in the database. We hand you the wording to drop into the register of processing activities.
Duration follows scope: a CRM for one sales team goes live far sooner than a portal wired to accounting, with an intranet and automation on top. Once the workshop is behind us we commit to dates in the contract.
Two or three sessions over video with whoever sells and whoever delivers. We come away with the journey of a deal, a list of everything keyed in by hand, and the ground rules set down in writing.
Pipelines, fields, permissions, mailboxes, website forms. First whatever nobody can work without. Automation and dashboards wait for the next phase.
The client list imported after de-duplication, live deals, attachments worth keeping. Anything with no remaining purpose stays outside instead of cluttering a brand new portal.
Short sessions by role, using your own live files, followed by an agreed period of support during which we adjust the setup as feedback comes in.
The first enemy of a CRM is double entry. As long as a deal has to be logged in the portal and then copied into a spreadsheet for the Monday meeting, teams pick the spreadsheet and the portal empties inside three weeks. Before adding a single feature we therefore hunt down whatever gets typed twice: the follow-up scribbled in a notebook, the quote rekeyed into the invoicing software, the monthly figure rebuilt by hand the night before the meeting.
Someone able to settle an argument: a sales lead, an office manager or the founder, depending on how big the company is. They resolve conflicting requests, restate the ground rules and send changes our way. Without that person everyone reinvents a private method, and after two quarters the portal resembles nothing at all.
One pipeline, a handful of mandatory fields, the mailboxes. Projects that launch CRM, tasks, holiday approval and electronic signature all at once seldom reach the end. The next module opens only after the previous one has become second nature.
On time spent, at EUR 95/hour excl. VAT. A costed estimate follows the scoping workshop. A CRM foundation for one sales team amounts to a few days of work, while the accounting link, the intranet and the automation are priced on their own. You approve each phase before we start it.
We bring it over, but we clean it first: duplicates, contacts with no named person or address, companies that no longer exist. People whose data you have no further reason to hold do not travel into the new portal. GDPR requires that, and it is incidentally the only route to a database worth using.
Where your operator publishes a Bitrix24 app, or lets us connect over SIP, each call lands on the matching record and anything missed raises a task to ring back. We set that up remotely from the parameters your operator supplies. Hardware installed on your premises is not something we touch.
Describe the way sales are organised, the number of users expected and the accounting package already in place. You get a first-phase scope and a running order.
Message received
An answer follows inside one working day. Report an outage that is stopping people working and it moves ahead of everything else.
Nothing here under that name. Check the spelling, or simply choose the nearest large city instead. Since every engagement runs remotely, whichever you pick changes nothing about what we do for you.