How involved does our team need to be?
Quick answer
We need one point person, access to the tools the workflow touches, and your team in two reviews, the UI review and the system review, so what we build matches how they work. Everything technical, the engineering, monitoring and maintenance, is ours. After launch, your team sets the rules and the approval level for each workflow.
Here is where your team shows up during a custom build.
- Your free AI audit. A thirty minute call with Mudi. You bring one recurring marketing workflow.
- Access. The tools the workflow touches, so the tool can work inside them.
- UI review. You see the interface your team will use before it is finished, and say what to change.
- System review. We walk your team through the working automation end to end, including where the approval gates sit.
- Delivery and training. It goes live in your team's hands, and we train the people who use it.
The two reviews are there so what we build matches how your team works. A tool that looks right to us and wrong to the people using it is the failure they exist to catch.
Between those points, the work is ours. You need no engineering team of your own at any stage: we handle the engineering, monitoring and maintenance.
After launch, the line is clear. Your team sets the rules and the approval level for each workflow. Changes to the system itself come through us, and Sharpen, the monthly plan, covers them.
Last reviewed by Mudi Elsaid