How does a custom build run, step by step?

1. Your free AI audit. A thirty minute call with Mudi. Bring one recurring marketing workflow, and we identify the manual steps, the tools involved and whether a custom build is worth scoping.
2. The full workflow audit and architecture. The paid first stage, if there is a fit. We map the work, rank where AI automation returns the most, and agree the scope before anyone builds.
3. UI review. You see the interface your team will use before it is finished, and say what to change.
4. System review. We walk your team through the working automation end to end, including where the approval gates sit.
5. Delivery and training. It goes live in your team's hands, and we train the people who use it.
6. Sharpen (Upgrades & Support). The monthly plan after launch. We host it, monitor it, fix it when it breaks and keep improving it with what we learn from similar builds for other teams.

From the audit to live usually takes about three weeks, and your own timeline is agreed in the scope. The build is priced per scope after step two and paid upfront, so the price is set before the build begins.

Your team is in the loop at the moments that need it: one point person, access to the tools the workflow touches, and the two reviews in steps three and four. How involved does our team need to be? covers that in full.

New workflows and major features after launch are quoted separately. Everything else that keeps the tool working is Sharpen's job.