amoCRMKommo

Reform widgets:
implementation best practice
in one click

Solutions we built by hand for years on Kommo and amoCRM projects — now installed from the marketplace and set up without a developer.

Why we build widgets

A widget should solve the whole problem, not part of it

Nikolay Kibets
Nikolay Kibets
Co-founder of Reform, business process architect, head of implementation

The widget market has long been split: some companies build widgets, others implement CRMs. Even where both exist, they are separate teams, and the people who see sales teams from the inside every day don't design the widgets.

That's why a widget often covers only part of the task — adjacent scenarios aren't thought through, edge cases are missed, and the rest still gets built by hand.

At Reform we are business process architects, and we build widgets as implementers: we solve the task on a real project first, then put everything that usually has to be added later into the widget.

Born in real projects

Every widget first worked for clients as part of a project. Only what's proven on real sales teams makes it into the catalog.

Thought through

We cover what usually has to be added later: lunch breaks and night shifts, the client's own manager, vacations, team leads without admin rights.

No developer needed

A team lead sets the rules in the CRM interface. No custom work, no specs.

Support from implementers

Questions are answered not by operators but by the team that built the widget and implements it for clients.

Why Reform

Not CRM technicians — business architects

We design sales team processes and automate them in Kommo and amoCRM. Widgets are part of this work.

Services at reform.bz
>8 yearsbringing order to sales teams across industries
2000+processes designed and implemented
45+successful implementations in operating businesses
5000+licenses of leading vendors sold
Catalog

Reform widgets

1 widget
01
KommoamoCRMFree

Schedule by Reform

Leads go only to people who are at work right now.

  • Staff schedule with shifts, lunch, vacations and night shifts inside the CRM
  • At night, leads go to whoever starts first — with a task at their shift start
  • Weighted queues: 60% to one, 40% to another, backups when the main ones are away
  • Grab: a new lead pops up for everyone at work — the fastest one takes it
#lead-routing#team