Pain and outcome first
Then scope. No spec? I’ll help you write it in plain language. I don’t stretch the job to someone else’s list.
Development services around your process
Pick a direction. I’ll unpack what’s included and which case sits next to it. The filter is the same: the team should earn more, not learn someone else’s box.
Krasnoyarsk, Moscow time. Remote across Russia and abroad.
Sales systems
I assemble a system around how you sell or run ops: statuses, roles, the deal card, dashboards. I don’t squeeze the business into Bitrix or amo.
- Funnels and objects for the niche: sales, families, schools, stock
- Sales lead and reps live in the UI from day one
- Integrations in the core, not widgets on tape
- Close the main pain first and grow modules
Bot scenario builder
Visual BotFlow: a site trigger, steps, a channel condition, a note on the deal. A marketer changes the branch themselves.
- Node graph: message, buttons, pause, write to CRM
- Triggers: bot command, event, landing lead
- Several bots on one loop
- Template “site lead → card”, no ticket to engineering
Survey builder
Your own survey builder: steps, branches, cover, a public link. A person fills the form — the deal already has answers and tags. Not a builder widget into a spreadsheet.
- A step editor with logic, no developer for every question
- CRM tags and funnel on the answers
- Analytics: started, finished, where they dropped
- Archive without losing answers
Sites, storefronts and analytics
I build the site around a real deal: storefront, form, the lead’s path. Plus own analytics — which sections people watch and where the lead went, not only Metrika numbers.
- Catalogue, product page, cart or RFQ for your type of sale
- Attention map by section and a form funnel
- Leads straight into CRM or a bot scenario
- Marketer access without the whole admin
Telegram, WhatsApp and channel hubs
Mini Apps, bots, several Telegram and WhatsApp accounts. The channel becomes an entry into the process, not a dump of chats.
- Several connections of one type on the loop
- Chat and files on the deal card
- Alerts for managers and a Mini App for the field
- Wired to the site, the survey and statuses
Content automation
A content factory: a post is born from the catalog, moves through kanban, goes to the platforms. A cloak link survives a storefront change.
- Product catalog and media as the source of posts
- RU+EN draft generation plus a manual composer
- Kanban: preview, approve, on air
- Clicks and ER by platform, not in three sheets
Agent logic and SaaS MVP
An agent with a knowledge base, qualification and a write to CRM. A stand to test a hypothesis, or a custom fit for your process.
- RAG over your materials, not abstract ChatGPT
- Scenarios, handoff to a human, token control
- Channels: widget, Telegram, WhatsApp
- SaaS MVP or a personal rollout
Aftercare
When the loop is already in production: fixes, stability, new ideas. Tight support instead of a just-in-case payroll.
- Priority fixes and module growth
- We watch stability and bottlenecks
- New features from real user pain
- A pace that fits you: point work or a retainer
Small and mid-size business — no price list at the door
We size the work from your goals and budget. Closing the main pain first is a valid start.
A small working loop
We close a narrow pain, look at the effect — and grow it when it makes sense.
Aftercare
Growth after launch without hiring a “just in case” department.