Best Practices
Tips, workflows, and lessons learned from agencies successfully using Agency OS
Learn from agencies already using Agency OS. This guide shares proven strategies, common pitfalls to avoid, and tips for getting maximum value from your system.
Getting Started Right
Week 1: Learn & Explore
Don't rush to production. Take time to understand the system:
✅ Do:
Complete the "Your First Steps" tutorial
Explore all sections with sample data
Click through every page
Test the "View as" feature
Try creating test records
❌ Don't:
Delete all sample data immediately
Start customizing before understanding defaults
Invite real clients in first week
Import all your data on day one
Goal: Understand how Agency OS works before using it for real.
Week 2-3: Soft Launch
Start using alongside existing tools:
✅ Do:
Add 2-3 real clients
Create current active projects
Start logging time
Have team create and update tasks
Run both systems in parallel
❌ Don't:
Abandon old system completely
Expect perfection immediately
Force everyone to use it
Get frustrated with learning curve
Goal: Build confidence while maintaining safety net.
Week 4: Go Live
Make Agency OS primary system:
✅ Do:
Announce official launch to team
Retire old project tracking
Invite first friendly client to portal
Establish daily habits (check tasks, log time)
Celebrate early wins
❌ Don't:
Keep maintaining two systems
Let people opt out
Skip training stragglers
Ignore feedback
Goal: Full commitment and adoption.
Team Adoption
Making It Sticky
Morning Standup in Agency OS:
Start meetings with Home → My Work tab
Review Task Summary KPIs and My Tasks
Update statuses live during meeting
Makes Agency OS the daily habit
Replace Slack for Project Updates:
Use task comments instead of Slack threads
Context stays with the work
Searchable history
Clients can see (when using Reply)
Make Time Tracking Non-Negotiable:
Daily expectation, not weekly
Start/stop timers in real-time
Review at end of day
Tied to invoicing and profitability
Celebrate Portal Wins:
When client praises portal, share with team
When status email avoided, highlight it
Track metrics: logins, comments, satisfaction
Show ROI of adoption
Common Objections & Solutions
"It's another tool to check" → Make it THE tool, not another tool
Morning standup starts here
All project info lives here
No need to check multiple places
"Takes too long to update" → Use action buttons for speed
"Start" button = one click to update status
Time tracker = auto-logging
Comments = faster than email threads
"I prefer spreadsheets" → Show the power
Relationships between data (not copy/paste)
Real-time updates (not stale exports)
Client portal (can't do that in sheets)
Filtering and views (more flexible than sheets)
"Clients won't use the portal" → Train them well
Start with one friendly client
Short walkthrough call
Quick wins (they see progress immediately)
Gentle nudging ("I've updated your portal!")
Training Resources
Create:
10-minute walkthrough video
One-page quick reference
GIFs for common tasks
FAQ document
Assign Champions:
One per team/department
They learn deeply and help others
First line of support
Gather feedback
Regular Check-ins:
First month: Weekly team Q&A
Office hours for questions
Share tips in team chat
Update training based on questions
Data Hygiene
Daily Habits
Update Status in Real-Time:
Move task to "In Progress" when you start
Mark "Done" when finished
Don't wait until end of day
Keeps everyone informed
Log Time Immediately:
Start timer when beginning work
Stop when switching tasks
Log manually if you forgot
Don't try to remember Friday what you did Monday
Add Context to Comments:
Explain the "why" not just "what"
Add enough detail for others
Use Reply for client-visible updates
Use Note for internal coordination
Weekly Habits
Review Your Tasks:
Check upcoming due dates
Identify blockers
Request help if overloaded
Update estimates if needed
Update Project Health:
Review project progress
Update Project Health badge (On Track / Needs Attention / Critical)
Check Budget Health % on active projects
Communicate changes to clients via Reply
Client Portal Check:
Use "View as" for each active client
Check for unanswered Reply comments
Ensure nothing looks stale
Update before client meetings
Archive Completed Items:
Mark projects as "Completed"
Keep completed tasks — don't delete
Maintain clarity in active views
Monthly Habits
Deep Clean:
Review overdue tasks (close or reschedule)
Update company statuses where needed (Client, Past Client, Lost)
Check for duplicate contacts
Review and clean up expense categories
Data Audit:
Ensure all projects linked to clients with an Engagement Type set
Verify time entries linked to tasks
Check that team Hourly Rates are current
Fix any data quality issues
Workflow Review:
Are automations working?
Any errors in workflows?
New automations needed?
Retire unused automations
Naming Conventions
Consistency makes everything easier to find and understand:
Projects
Format: [Client Name] - [Project Type]
✅ Good:
"Acme Corp - Website Redesign"
"TechStart - Brand Identity"
"LocalCafe - Monthly Retainer - Q1 2025"
❌ Avoid:
"Website" (which client?)
"Project 1" (meaningless)
"The new site for Acme" (too verbose)
Tasks
Format: [Verb] [Object/Deliverable]
✅ Good:
"Design homepage mockup"
"Write blog post about AI"
"Review contract with legal"
"Deploy production update"
❌ Avoid:
"Homepage" (what about it?)
"Work on the thing" (what thing?)
"URGENT!!!" (use the Priority field)
Deals
Format: [Company] — [Deal Description]
✅ Good:
"Beacon Digital — Q2 Retainer Renewal"
"TrueNorth — Employer Brand Refresh"
❌ Avoid:
"New deal" (for which company?)
"Website project" (which client, which project?)
Interactions
Format: [Company] — [Deal Name] - [type]
✅ Good:
"Beacon Digital — Q2 Retainer Renewal - call"
"TrueNorth — Brand Refresh - email"
Communication Best Practices
Internal Team Communication
Use Notes for:
Technical discussions
Budget concerns
Timeline worries
Strategy questions
Team coordination
Use Reply for:
Updates on progress
Questions for the client
Deliverable ready notifications
Responses to client questions
Default to Note: When in doubt, use Note. You can't unsend a Reply that clients see.
Client Communication
Proactive Updates:
Don't wait for clients to ask
Update portal regularly
Use Reply at milestones
Keep them informed
Response Times:
Reply to portal comments within 24 hours
Set expectations clearly
Use email for truly urgent issues
Portal for everything else
Training Clients:
Walk them through on kickoff call
Send quick reference guide
Reply to first portal comment quickly
Gently redirect email questions to portal
Sample Redirect: Client emails: "What's the status on the homepage?"
Your reply:
"Great question! I've updated your portal with the latest progress. The homepage design is 80% complete and on track for Friday. You can see all the details here: [link to portal]
Feel free to add any questions directly on the task and I'll respond there so we keep all the context in one place!"
Workflow Optimization
Automate as you go
Agency OS connects to Noloco's native integrations (Slack, DocsAutomator, OpenAI, Stripe, Google Sign In) and to automation tools like Zapier, Make, and n8n for custom workflows.
Start with the highest-impact automations first:
High value, quick to set up:
Slack notification when a deal is won
Slack alert when Budget Health % drops below a threshold
Email client when invoice is overdue
Add next:
Auto-create a Google Drive folder when a new project is created
Auto-log Gmail / Google Calendar activity as Interactions in CRM
Weekly project summary email to clients
Level up later:
Monthly recurring invoice generation
New lead → notify sales team in Slack
All tasks complete → request client feedback
See Customising Your Agency OS for the full integrations guide.
Measuring Success
Efficiency Metrics
Track:
Time from project start to completion
Number of "status update" emails (should decrease)
Client portal login frequency
Time logged per project vs estimated
Targets:
Significant reduction in status emails
70%+ clients logging in monthly
90%+ of time logged within 24 hours
Estimates within 20% of actuals
Quality Metrics
Track:
On-time delivery rate
Client satisfaction scores
Number of revisions per deliverable
Scope creep incidents
Financial Metrics
Track:
Days sales outstanding (DSO)
Project profitability (Budget Health % across active projects)
Team Billables vs invoiced revenue
Revenue by engagement type (Revenue Dashboard)
Common Pitfalls to Avoid
1. Over-customising too early
❌ Mistake: Spending weeks customising before first project
✅ Better: Use defaults for 2-4 weeks, then customise based on real needs
2. Not testing "View as" before inviting clients
❌ Mistake: Giving clients access before testing with "View as"
✅ Better: Always test the client view thoroughly before sending an invite
3. Forgetting Reply vs Note
❌ Mistake: Writing "Client is being difficult" in a Reply comment
✅ Better: Always double-check before commenting. Default to Note.
4. Inconsistent time tracking
❌ Mistake: Trying to remember all hours on Friday
✅ Better: Start/stop timer in real-time, or log daily from Home → My Time
5. Tasks without due dates
❌ Mistake: Creating tasks with no due date set
✅ Better: Due dates are required — they power the Team Workload overdue view and the Missing Due Date KPI on Home
6. Poor task breakdown
❌ Mistake: Tasks like "Build entire website" (never gets completed)
✅ Better: "Design homepage", "Code navigation", "Add contact form" (specific, achievable)
7. Inviting all clients at once
❌ Mistake: 20 clients get portal access on the same day
✅ Better: Start with 1-2 friendly clients, perfect the process, then roll out
8. Stale Hourly Rates
❌ Mistake: Not updating team Hourly Rates when rates change
✅ Better: Update rates in the Team Cost tab whenever they change — stale rates mean inaccurate Budget Health % across every project
9. Abandoning too quickly
❌ Mistake: "This isn't working after 3 days"
✅ Better: Commit to a 30-day trial, address issues, iterate
10. Not celebrating wins
❌ Mistake: Taking adoption for granted
✅ Better: Recognise team members using it well, share client praise, highlight status emails avoided
Scaling your Agency OS
5-10 people
Focus on:
Basic structure works perfectly
Simple workflows
Clear communication habits
Consistent time logging
10-25 people
Add:
More granular project ownership (Lead field)
Team Workload reviews in weekly standups
Stricter naming conventions
More automations
Consider:
Enabling the Departments page (Build Mode → Navigation) to organise the team by function
Dedicated person responsible for Agency OS admin
25-50+ people
Implement:
Full department structure (unhide Departments in nav)
Offices page if multi-location (unhide in nav)
Advanced role customisation
Resource capacity planning using Team Workload
Integration with accounting software
Tips from successful agencies
"Start with Projects Only"
Sarah, 15-person design agency
"We ignored CRM for the first month. Just focused on delivering projects well. Once that was solid, we added sales tracking. Trying to do everything at once was overwhelming."
"Champion the Portal"
Michael, 30-person development agency
"Our account managers became portal evangelists. When clients emailed for status, they'd reply: 'I've answered in your portal at [link].' Took 2 months, but now clients check the portal first."
"Make Time Tracking Non-Negotiable"
Jessica, 20-person marketing agency
"We made time tracking mandatory from day one. Now we actually know which clients and project types are profitable. Game changer for pricing."
"Portal = Competitive Advantage"
Chris, 40-person digital agency
"We demo the client portal during sales pitches. Prospects see transparency and professionalism other agencies don't offer. It's closed multiple deals."
"Customise Your Language"
Amanda, 12-person branding agency
"We renamed 'Projects' to 'Engagements' to match how we talk. Small change, but the team adopted much faster when it felt like ours."
Your first 90 days
Days 1-7: Foundation
Days 8-30: Real data, real habits
Days 31-60: Client portal
Days 61-90: Optimise & scale
Getting help
Nola AI Assistant — ask Nola to help you navigate or customise
These guides — comprehensive coverage of every section
Book a call — schedule onboarding support with the Noloco team
In-app chat — contact Noloco support at any time
What's next?
Ready to extend and connect Agency OS to your existing tools? Head to Customising Your Agency OS for the full guide on Build Mode, integrations, and optional extensions.
Last updated
Was this helpful?