What We Build
- Forecasts of sales, demand, and warehouse or call center workload.
- Probability scoring: a lead will convert, a customer will churn, an order will be returned.
- Classification: automatically routing requests, products or documents into categories.
- Recommendations for products, services or content on your website and in email campaigns.
- Customer segmentation by behavior and anomaly detection in sales, payments or technical metrics.
When You Don't Need an ML Model
We'll tell you honestly if the problem can be solved more simply. Machine learning is unnecessary when:
- the rules are obvious and stable: "wholesale customers get a discount" doesn't need a model;
- there's too little data: a few hundred records usually aren't enough for a model to learn anything useful;
- the output has nowhere to go: a forecast nobody sees in their daily work won't change a single decision;
- you need to explain causes rather than predict outcomes: solid data analysis is often enough here.
A model also can't predict a future that never appeared in your data, such as a new competitor or a change in regulations. A forecast is guidance with a certain level of accuracy, and we say plainly what accuracy to expect.
What Data We Need
There's no exact number, but a seasonal forecast needs history covering at least several full seasons. Lead scoring needs not only the leads but also the outcome, whether the customer bought or not. Quality matters as well: if statuses in your CRM are set at random, the model will learn from those mistakes. That's why we always audit your data before training and tell you what you can realistically expect from it. External data such as holidays, weather or ad campaign schedules often helps explain spikes.
How We Verify the Model Works
We evaluate the model on data it didn't see during training. For forecasts, we use the most recent period as if we had made the forecast in advance, and compare it with what actually happened. The key comparison is with the simple method you use today, such as "same as last year" or a manager's experience. If the model isn't noticeably better than that, we say so, and it isn't worth deploying.
How the Model Gets Into Your Work
- Forecasts are written to a spreadsheet or data warehouse where they show up in reports.
- A lead score is added to your CRM so reps see it on the customer record.
- Recommendations are connected to your website or app via API.
- Scheduled forecast updates and anomaly alerts are set up.
If a language model is a better fit than a classic model, for example for processing the text of support requests, that falls under AI integration for products.
What to Prepare on Your Side
- A description of the decision you want to improve and the people who make it today.
- Access to historical data: sales, leads, customers, inventory, for the longest period available.
- Context on anything unusual: when prices, product range or business rules changed, and any gaps in record-keeping.
- A person on your team who can help check whether the model's results make sense.
What Affects the Cost
- Data readiness: a ready-to-use dataset, or data that needs to be collected and cleaned from several systems.
- Task complexity: a single forecast of total sales, or forecasts for thousands of products across several regions.
- Integration: a report with results, or integration into your CRM, website or inventory system.
- Update frequency of forecasts and response-time requirements.
- Support: accuracy monitoring and retraining after launch.
We often suggest starting with a pilot on your data. It shows whether the required accuracy is achievable before you invest in a full rollout.
Frequently asked questions
What accuracy do you promise? None in particular until we've reviewed the data. Accuracy depends on whether patterns actually exist in your history. After the pilot, you see real numbers on your own data.
Can we use off-the-shelf services instead of a custom model? Sometimes, yes, and it's cheaper. For example, some ecommerce platforms already have built-in recommendations. A custom model makes sense when ready-made solutions don't account for the specifics of your business.
What do you build models with? Mostly Python and SQL, with tools chosen to fit the task and your infrastructure.
Who will own the model? You will. The code, the trained model and the documentation are handed over to you.
Will the model need maintenance after launch? Accuracy can degrade as the market changes, so we monitor it on new data and retrain the model when behavior shifts noticeably. We agree on this support in advance.
Why Promodex
A model only delivers value when it is built into your website, CRM or reports, and our in-house team builds and supports those systems. Since 2015, we have delivered 750+ projects in development, design and marketing. We start by asking whether you need a model at all, compare it against simple methods, and never push you to deploy something that doesn't make a real difference.