Design the operational runsheet for onboarding a new customer: steps, owners, timing, the customer's view at each stage, and where onboardings stall.
Design our customer onboarding runsheet. What happens today: {{current}} (steps, who does them, typical timeline, where it goes wrong). The moment a customer gets first value: {{first_value}}.
Build: the runsheet — every step with owner, trigger, SLA, and the customer-visible artifact ('what do THEY see/receive at this point?'), the critical path to first value (compress everything on it; everything off it can wait), the stall points from my notes with unsticking mechanisms (auto-reminders, escalation after X days silent), the kickoff communication templates (welcome, what-happens-next, chase), and the health signal per stage that flags an onboarding going sideways before the customer says so. Include the internal handoff points — that's where most onboardings die.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekCompare options against weighted criteria to decide.
Turn 'how we do this around here' into a standard operating procedure anyone can follow on their fir...
Onboard a new supplier properly: the verification file, the terms confirmed in writing, the trial-or...
A sustainability audit that finds real savings: energy, waste, and procurement wins ranked by paybac...
Plan the end-of-year shutdown: customer notice, leave mechanics, skeleton coverage, and the January...
Audit your SaaS stack for overlap and waste: the inventory, the consolidation candidates, and the mi...