Building a marketing system and sales department at SkladBot
Product
A cloud platform that automates fulfillment warehouse operations: app.skladbot.ru.
Role
Marketing and Sales Lead. Team of ten. Worked across the founder, Sales, Implementation, and Support teams. Owned the customer journey from research and acquisition through sales, implementation, and retention.
Situation
The product was just entering the market, so systematic marketing and sales processes had not yet been built. Most customers came through the founder’s personal network and speaking engagements, while inquiries were handled inconsistently.
Constraints
- No stable customer acquisition system.
- The sales process was intuitive and undocumented.
- The manager spent up to six hours a day on product presentations alone.
- No structured onboarding, implementation, or post-sale support.
- Scaling sales required proportional team growth.
Objectives and solutions
Acquisition
Objective
Build a customer acquisition system that does not depend on the founder’s personal network.
What I did
- Conducted 20 interviews with active and former customers. Analyzed the reasons behind purchase, implementation, continued use, and churn.
- Only two of the 20 customers cited technical issues as the reason for leaving. Another 15 had not understood the system or integrated it into their daily work.
- Used the research to segment customers, position the product, design sales scenarios, and communicate value on the website and in presentations.
- Developed the go-to-market strategy and marketing funnel. Created the website, articles, videos, emails, and lead magnets.
- Built an industry community for fulfillment business owners as a separate touchpoint with potential customers.
Sales
Objective
Build a sales process that can scale without proportional team growth.
What I did
- Mapped the process from a new inquiry to payment for implementation.
- Introduced lead scoring, consistent presentation rules, post-meeting follow-ups, and a unified CRM workflow.
- Defined the objective, manager actions, result, KPI, and transition rules for every stage.
- Created the complete sales content stack: product presentation, emails, scripts, and commercial proposals.
- Formalized CRM operations and the transfer of customer information between stages.
Activation
Objective
Ensure that customers not only pay for the product, but implement it and use it regularly.
What I did
- Built a dedicated implementation process for the first 30 days after payment.
- Separated ownership between Sales and Implementation and documented the customer handoff.
- Defined the setup, training, support, and usage-control stages.
- Established successful implementation criteria and activation KPIs.
- Created an implementation plan, instructions, reference materials, training content, and automated customer messages.
- Built a Telegram support bot that answers common customer questions.
Retention
Objective
Reduce churn and improve retention through regular product usage and systematic analysis of churn reasons.
What I did
- Introduced controls for the transition from the first month to the second and beyond.
- Built a system for collecting and analyzing the reasons behind refusals and churn.
- Established rules for handling implementation blockers, problems, and critical customer requests.
- Connected sales, implementation, and support data to customer-process improvements.
- Defined KPIs for retention and regular product usage.
Automation
Objective
Reduce the dependency of revenue growth on team size.
What I did
- Introduced customer scoring to filter out poor-fit inquiries before the product presentation.
- Created a video presentation that introduces the product without a manager’s involvement.
- Prepared automated emails and materials to guide customers through the sales stages.
- Built a Telegram support bot that answers common product questions and reduces the support team’s workload.
Results
Acquisition
- The number of leads booking a product presentation increased by 32.2%.
- Organic traffic increased by 110%.
- An industry community of 800 business owners became a source of UGC, which we turned into lead magnets and used to generate inquiries.
- Lead magnets account for 3% of all inquiries.
Work artifact: existing customer interview scriptOpen
A small excerpt from the research script is shown without sensitive data or metrics.
Existing customer interview script
We identify jobs through people’s actions. The goal is to uncover those actions and use them to define a segment.
Segment = long-term customers ∩ customers with smooth implementation ∩ processes that the product fits perfectly.
Ideal JTBD scenario v4.0
- Contextcontext + background
- Switch triggerstruggling moments + push forces
- First interaction with the solutionhiring moment
- Real processesjob execution
- Workarounds, failures, and constraintsbarriers + anxieties
- Training and implementationonboarding JTBD
- Benefits and progresspull forces + desired outcomes
- Segmentationcore ICP detection
Sales and revenue
- Revenue grew by 100% year over year.
- Sales were moved to a unified process with scoring, CRM, KPIs, and control points.
Work artifact: sales business processOpen
A small excerpt is shown without sensitive data or metrics.
| Stage | Objective | AMO task | Stage result | Message |
|---|---|---|---|---|
| New inquiry | Move to scoring | Call within 30 minutes. Move the lead to “In progress”. | Customer reached by phone. | Hello, thank you for your inquiry. A manager will call within 30 minutes to discuss the implementation process. |
| Scoring | Identify needs and filter out poor-fit leads | Run the scoring script, add notes to the customer card, and send a follow-up within two hours. | A decision is made: schedule a presentation or decline. The customer’s jobs and problems are clear. | Summarize the conversation: customer job, problem, implementation owner, presentation date, and customer-side participants. |
| Presentation | Show how the system solves the customer’s processes and move them to implementation | Send a follow-up within one hour after the presentation. | The customer workflow and selection criteria are understood. The product is demonstrated in the context of the customer’s needs. | Summarize the problem, selection criteria, and implementation process. Record a specific first-month scenario and outcome. |
Work artifact: sales manager playbookOpen
A small excerpt is shown without sensitive data or metrics.
- Our customer
- Automated emails
- Product presentation script
- Conversation framework
- Job discovery
- Showing how the system handles these jobs
- Closing
- Important details
- Sales approach
- Sales process
- Solution
- Flow
- Rules for handling inquiries
- Pre-demo lead qualification
- Purpose of scoring
- Rules
- Running the presentation
- Presentation template
- Introduction — 3–5 minutes
- Current processes — 5–7 minutes
- Job and desired outcome — 3–5 minutes
- Solution demo — 10–15 minutes
- Implementation format — 5 minutes
- Launch terms — 2–3 minutes
- Next step — 1–2 minutes
- Checklist
- Before
- During
- After the presentation
Activation
- Sales and implementation were combined into one process covering the first 30 days after payment.
- Separate activation KPIs and successful launch criteria were established.
- Implementation became a structured process with setup, training, support, and control points.
- Activation increased by 20%.
Work artifact: implementation business processOpen
A small excerpt is shown without sensitive data or metrics.
| Stage | Timing | Objective | AMO task | Stage result | Message |
|---|---|---|---|---|---|
| New customer ready for setup | 1 hour | Notify the responsible manager about a new customer | Collect customer data. Review problems, processes, jobs, and blockers. Send a welcome message and links. | A customer group is created. | Confirm payment and send account access, the support link, and the customer video guide. |
| Implementation plan | Immediately after creating the Telegram group | Show the customer what will happen during the first month | Send the implementation plan PDF. | The plan is sent and understood. | Send the monthly work plan and explain how each action contributes to successful implementation. |
| Initial customer data | 1 day | Prepare the account before the setup call | Send specific instruction links and receive confirmation that the customer is ready. | The customer has entered the data needed for setup and demonstrations. | Ask the customer to enter company details, register the company, add a client, configure integrations, and connect the required services. |
Retention
- Introduced controls for the transition from the first month to the second and beyond.
- Built a system for collecting and analyzing the reasons behind refusals and churn.
- Established dedicated retention KPIs and rules for customers at risk of leaving.
- The share of customers advancing to the next month increased by 20%. Customer retention increased from 2.4 to 3.8 months.
How the objectives were solved
Increasing customer lifetime
- Problem. Customers used the product for an average of 2.4 months. Churn was high after the first few months.
- Hypothesis. The support team cited two reasons: unique customer processes that did not fit the system and technical product issues.
- Test. Conducted 20 interviews with active and former customers and systematized the reasons for churn.
- Finding. Only two customers cited technical problems. Another 15 had not understood the product or integrated it into daily work.
- Solution. Rebuilt implementation around a dedicated manager, a 30-day plan, training, usage monitoring, and mandatory churn analysis.
- Result. Average customer usage increased from 2.4 to 3.8 months.
2024 vs 2025
Traffic
- Unique visitors
- ↑ +105%
Traffic sources
- Referrals
- ↑ +173%
- Organic
- ↑ +110%
- Direct
- ↑ +51.7%
- Telegram
- ↑ +5%
Telegram subscribers
- Group
- ↑ +200%
- Channel
- ↑ +67%
Conversion by source
- chatgpt.com
- 13.3%
- Organic
- 3.4%
- Lead magnets
- 3.4%
- Telegram
- 2.4%
Leads
- Total inquiries
- ↑ +32.2%
Revenue
- Total receipts
- ↑ +100%