Pipeline to invoice
Six stages, and di record no dey restart
Most pipelines stop for 'won', wey be strange place to stop — like recipe wey end when oven don on. Di interesting part na wetin happen between winning di work and getting paid for am, and na usually there di retyping dey start.
Count how many times customer name, address and telephone number dem type am for dat journey for normal company. Di honest answer na usually four: into di CRM, into di calendar, into di payment link, into di invoicing software. Each retype na chance to bring typo, and each typo na chance for invoice make person wey im job na to reject invoice reject am.
Here di number na one. Di customer type am.
Booking no be separate universe
For anybody wey im product involve to show up somewhere, di booking na di deal. To hold slot, confirm am, remind customer di evening before — all of am hang on di contact, so di reminder know which conversation e belong to and di seller fit see say e go.
Wetin dat one mean sef be say cancellation no be mystery. E appear for di thread, with time, beside di message wey di customer explain why. Whether dat reason true na between you and dem.
Payment, for di seller own account
To collect money na service for di family, no be plugin wey dem bolt on: di charge go to di seller own account, and di record of am land back on di contact. Di person wey do di work fit see say dem pay am without to ask office, wey remove one whole genre of internal e-mail.
- ✓Quoted2 400 zł, valid 14 days. Dem send am from di thread, so di customer reply am on di thread.
- ✓BookedConfirm by e-mail; reminder send Friday evening. Dog note.
- ✓Don pay2 400 zł by card, inside di seller own account.
- ✓Invoice don go outE come from di contact. Nobody type address.
Time wey don pass: 11 daysRetype: 0
About di invoice, and about KSeF
Invoicing na im own service inside di castomo family, and iKonekt give am record wey already get di customer, di price wey dem agree on, and wetin dem actually do. Na di whole trick be dat: invoice no be creative work, na just show of facts wey already dey somewhere.
For Polish sellers, e include KSeF, di national e-invoicing system. Di date wey di obligation go start depend on di company, so dem configure am per tenant instead of to switch am on for everybody at once — wey be di polite way to say say we no go make your accountant calendar our design decision.
On di matter of accountants: every one wey we don talk to get di same request, and e no be feature. Na "abeg stop to send me spreadsheets wey get three versions of di same address inside". Take dis page as formal promise.
Wetin di six stages no be
Dem no be sales methodology, and iKonekt no get opinion on whether your deal dey 40% or 60%. Stages for here dey describe wetin don physically happen to a record: a slot either dey held or e no dey, an invoice either don raise or e no raise. To forecast from facts na somebody work. To invent di facts na nobody own.
Di record wey start as chat message fit end as paid invoice.
Same record, same thread, same customer. No export, no import, no evening wey you go spend to reconcile two systems wey no agree.
"We go raise di invoice on Monday."
Dem raise am on Saturday, at 11:21.
Di same record from di first chat message to di paid invoice. Nobody type di address di fourth time, and di customer never notice any seam — because e no dey.
Wetin dey hold everything apart →