A CRM for a SaaS provider: subscriptions from the platform, client onboarding and 1C settlements
The sales team of an e-signature SaaS service could not see in the CRM how many signatures a client had left or which plan they were on: this data lived only in the platform itself. New companies were set up in the platform by hand, and invoices and payments had to be moved between the CRM and 1C manually.
Cloud Bitrix24 — REST API and webhooks only, no core access. The platform sends the state of all companies in one batch, one company can pay for services on behalf of another, and 1C reports not only the posting but also the cancellation of a payment document.
- A platform webhook receiver: the subscription pipeline is indexed in batch, and the remaining signatures and plan are updated by company id — only if the values actually changed
- Mapping of 10 platform plans, with an unknown one becoming "Custom"; a new company gets a deal at a stage based on its signature count, written with three attempts
- One-click onboarding from the deal: details, contacts and addresses are validated, the company is registered in the platform, its id is returned to the CRM, errors go to a comment
- Exporting a smart invoice to 1C as a single JSON: product rows, business ID (BIN) and bank details, legal address, contract number and the responsible manager
- Payments from 1C go into a "Payments" smart process: an item with a product row per service, payer and service recipient kept separate, duplicates filtered out by document number
- Cancelling a payment document in 1C removes the linked payments in the CRM; the exchange is logged, and a debug mode allows checking data without sending it to 1C
Each client's remaining signatures and plan are visible right in the CRM, and new companies immediately land at the right stage by subscription volume. An invoice goes to 1C from the card, and the payment returns to the CRM with product rows — with no manual transfer between systems.
Related services and solutions
Bitrix24 D7: boxed development and stabilization
I work not only with interface settings, but at the level of the box, the code and internal APIs.
Business process automation
When employees transfer data manually, reconcile spreadsheets, lose requests or repeat the same actions — I turn the routine into code.