01
Prerequisites live elsewhereAdmins leave the feature to fix platform, identity, mail, security or data dependencies.
Problem
Customers need to complete setup before they can use a feature
Enabling a SaaS feature can require documentation, permission changes and prerequisite checks across several admin tools. I explored how to guide admins through that work without making them reconstruct the setup process themselves.
Feature shippedReady for setup
DocsPermissionsAdmin center
Customer valueOnly after activation
Traditional enterprise setupSteps required to enable one feature
Step 2 of 10Complete prerequisitesSeveral requirements must be configured before this feature can run.
✓AI servicesReady
!Application identityRequires another admin surfaceOpen admin center ↗
!Data policyReview connector permissionsView documentation ↗
!MessagingMailbox and sync requiredConfigure ↗
Admin workThe admin must resolve prerequisites across several tools.
02
Admins translate documentation into actionsInstructions have to be translated into product actions before a decision can even be made.
03
System language comes firstRoles, policies and rules expose the product model before the admin understands the business choice.
04
Each handoff can interrupt setupEach unknown term, new tab and unresolved dependency becomes another place to stop.
The business problem
Setup is part of the adoption journey
Confusing prerequisites and handoffs can cause admins to abandon setup. I treated completing setup as a step toward adoption, with its own points of failure to address.
01ShippedFeature is available
→02Setup startedAdmin begins configuration
→FrictionAdmins may leave setup hereDependencies · terminology · handoffs
→03ActivatedFeature works
→04AdoptedUsers get value
Staying ahead is not only about shipping more. It is about getting more of what you ship into customers' hands.
Research
Mapping the real setup journey
Using enterprise CRM agent setup as a proving ground, the pattern became clear: one customer journey was spread across identity, data, security, messaging, rules, testing and deployment.
Feature setupOne customer journey
Identity
Data policy
Capacity
Security
Mail
Rules
Testing
The product knew more than the admin could see.
Prerequisite state existed across the platform, but the admin had to reconstruct it manually.
Some decisions should stay human.
Scope, autonomy, permissions and deployment carry business intent or risk. They need explicit judgment.
“Configured” was not the same as “trusted.”
Admins needed to see how the agent would behave before making it live.
Legacy boundaries could not simply disappear.
A credible solution had to work with existing ownership and admin systems, not redesign the entire platform.
Solution
An AI-guided setup experience
The assistant checks requirements against the customer’s environment, then builds a setup path. It completes routine steps, explains recommendations and asks for approval where required. Admins can ask questions about the decision on screen.
01Read requirements
02Inspect org state
03Build the path
04Translate decisions
05Act / recommend / stop
06Verify
07Test + deploy
The experience shift
Reducing the effort of complex setup
Traditional setup
- Read documentation
- Find prerequisites
- Jump across admin products
- Translate technical terms
- Configure rules and permissions
- Remember what is complete
- Troubleshoot and revisit
- Test and deploy
→
Setup with intelligence
- Inspect the environment first
- Reuse what already works
- Handle safe routine work
- Translate system language
- Ask only for judgment
- Preserve progress across handoffs
- Verify changes automatically
- Test before deployment
Human–AI boundaries
Clear boundaries between AI assistance and human control
Routine work the admin can inspect
Check prerequisites, reuse connections, translate selections and verify dependencies.
Recommendations based on the environment
Suggest scope, rules, qualification, routing and a sensible first configuration.
Decisions requiring approval
Scope, autonomy, permissions, policy boundaries and final deployment stay explicit.
Conversational guidance
Ask for clarity when something is unclear
Enterprise setup contains permissions, dependencies and platform language that will not always be familiar. The conversational layer lets the admin ask a question in the moment and get an answer grounded in the decision already on screen.
Question → Explanation → Admin decision✦Aurelis setup assistant
Agent authority · in progressConfiguring prospect activity access
What does read access actually let Pipeline Scout do?
It can understand previous seller conversations inside the scope you approve.It can’t edit customer records, change security settings or expand its own access.You stay in control of the permission.
✦Guided setup
3 of 7 · Prospect focusAurelis
I checked your environment first. Most prerequisites are already ready, so I only need your input where the business decision matters.
Recommended scopeNorth America + Europe136 sellers · 68% of inbound pipeline
Why these two regions?
Aurelis
They have complete seller access and the strongest inbound coverage. You can add other regions later.
AI handles the configuration•Admin can ask when unsure•Authority stays explicit
A necessary enterprise tradeoff
Handling setup across multiple products
How products are owned
Feature teamIdentity teamPlatform teamSecurity team
≠
How the customer experiences it
One setup journey→Working feature
Keep the setup connected across product boundaries
I kept prerequisite status visible in the setup. When an admin must use another product, the experience saves progress and checks the change when they return.
Key design decisions
Key design decisions
Inspect before asking
Check services, data, identities, permissions and capacity first.
Ask business questions
Let Mona choose regions and intent; translate that into configuration behind the scenes.
Pause for permission
Explain the scope and limits of access before Mona approves it.
Preserve progress across external steps
Save progress, explain the handoff and verify the change on return.
Review completed setup steps
Mona can revisit previous modules without losing the current conversation.
Test when the agent should stop
The simulation includes an ambiguous case the agent must hand back to a human.
Story
Meet Mona, a CRM administrator
Mona is a CRM administrator configuring Pipeline Scout for her team. The walkthrough shows how guided setup checks prerequisites and explains settings before asking her to make a choice.
Mona’s setup task
Mona’s goal: set up Pipeline Scout for her sellers
Pipeline Scout is a fictional AI agent in Aurelis CRM. Mona defines where it can operate, how it qualifies prospects and what it can do. The assistant handles the configuration around those decisions.
FoundationAre services, data and permissions ready?
ScopeWhere and for whom can it operate?
BehaviorWhich prospects can it work on?
HandoffWhat counts as qualified?
TrustHow should it behave before going live?
Working prototype
Try the guided setup
Use the prototype to experience the setup flow from start to finish. Choose the guided path, work through each setup module with the assistant, review the supporting details when needed, and test the configured agent before deployment.
1Start guided setupChoose Guided setup with AI from the Pipeline Scout setup page.
2Complete the 7 setup modulesMove through Foundation, Scope, Prospects, Autonomy, Qualification & routing, Knowledge, and Test & deploy.
3Review and validate along the wayUse the available links and details to understand recommendations, permissions, and the required external check.
4Run the testReview the test scenarios and verify the agent’s behavior before deployment.
Outcome
Business outcome
What the walkthrough suggests, and what I would measure
In the representative walkthrough, the guided path compresses a 35–45 minute setup into roughly eight minutes. In production, I would judge the idea by whether more admins activate the feature, fewer abandon setup, and usage continues after activation.
Traditional walkthrough35–45 minDocs + prerequisite checks + handoffs
Guided prototype~8 minAI handles routine work; admin decides
TraditionalMultiple handoffsAdmin carries progress
Guided1 necessary handoffProgress preserved + verified
↑ Feature activationMore admins reach a working, tested capability.
↓ Setup abandonmentFewer exits at prerequisites, terminology and handoffs.
↓ Setup support effortLess specialist support for repeatable setup work.
Beyond CRM
A reusable model beyond CRM
The same setup pattern could apply beyond CRM: check the environment, guide decisions, preserve progress across tools and test the configuration before deployment.
AI shouldn't only make SaaS products smarter after adoption. It can make complex SaaS products easier to adopt in the first place.
The design thesis
Make complex products easier to configure and adopt.
The setup should explain the decisions admins need to make and show whether the configuration is ready to use.