From my conversation with Lindsay Keys of Pavoi and Seb Debrouwere of DOSS. Read the full case study →
ERP projects have a reputation for long discovery phases and armies of consultants. Seb Debrouwere, VP of Business Development at DOSS, describes the usual route like this: a big price book, endless slides, a contract signed before you've seen the product, and then a second batch of consultants who start discovery all over again. He once sold a company before its ERP implementation had got through discovery.
DOSS built its process, which it calls Lead to Live, to move building and discovery to the front. Pavoi, the number one jewelry seller on Amazon and TikTok, started working with DOSS early, before parts of today's process existed.
Here are the six steps, each with what to ask any vendor for.
1. Start from a starter

DOSS has pre-built setups for typical businesses in each industry. Seb calls them "the sourdough starter of the baking process." The starters aren't locked modules. Underneath, DOSS works like "a box of Legos," so the data structures, workflows and building blocks can all be changed.
The starter aims to cover 80% to 90% of what a typical brand in a vertical needs. The project time then goes into what makes each business different.
What to ask for: what's already built for a business like yours, and what can be changed under it.
2. See a working draft before you sign
While a brand is still deciding, DOSS tries to build a draft of its system with real or mock data. The goal is for the brand to spend time in the product early, before the contract.
What to ask for: a draft you can use, built on your data, before you sign.
3. Refine the draft together
At the design kickoff, nobody starts from a blank page. DOSS's forward deployed team, a mix of engineers, product people and subject matter experts, works from the draft with the brand, using DOSS's own AI tools to configure and build. Seb says customers are usually in close, almost daily contact with DOSS during the build.
What to ask for: who will work with your team day to day, and how often.
4. Go live in stages
There's no hard cutover. Each workflow is tested and accepted, and the most critical ones go live first. The brand starts using the product while other parts are still being built.
What to ask for: which of your workflows would go live first, and why.
5. Spend the time on your problems
Could brands one day set up their system entirely on their own? Technically, yes, Seb says. He sees more value in the time people running the business spend with the people building it. Some people know their requirements exactly, and others are experts in their problems rather than in the solutions.
Seb wants that time spent on conversations like this one: "You have this huge volume of orders. How do we accommodate for the spikes? What is important for you with the rules?" Less of it should go to which formula goes where.
What to ask for: what your working sessions will be about.
6. Keep changing after go-live
When the business changes after go-live, adding to the system shouldn't be a long project. What DOSS builds for customers also goes back into the starter, so each new customer starts further along. A customer's own edge stays its own. "We're obviously not taking Pavoi's secret sauce and handing that out to the rest of the industry," Seb says.
What to ask for: what the last change a customer asked for after go-live involved.
More from this conversation



















