Real Scenarios. Before & After.
Twenty-two everyday situations that every team deals with — and how Delivery Hub makes each one easier.
1. Client submits a change request
Your client emails you asking for a new report. You forward it to the team. Someone adds it to a spreadsheet. A week later, the client asks for an update and nobody remembers where the thread is.
- Client sends an email describing what they want
- You forward it to the dev team in a separate thread
- Scope is discussed verbally in a meeting nobody records
- Client has no visibility until the next status call
- Client submits a Work Request directly in Delivery Hub
- The team reviews, estimates, and moves it to the board
- Client sees real-time status: approved, building, testing, done
- Comments and files stay attached to the work item — nothing lost
2. Small fix that shouldn’t need a meeting
A field label is wrong. Everyone agrees it’s a 5-minute fix. But it still needs to go through the full approval process, sit in a queue, and wait for the next sprint.
- Submitted as a ticket like everything else
- Waits for a committee to approve it
- Sits in the backlog for 1–2 sprints
- Three meetings before anyone touches the code
- Marked as Fast Track — skips the approval queue
- Developer picks it up the same day
- Fixed, tested, and deployed in days instead of weeks
- Full audit trail without the bureaucracy
3. Working with an outside vendor
You hire a consulting firm to build a feature. Now you’re maintaining two project trackers, copying tasks into spreadsheets, and manually syncing updates between systems.
- Export tasks to a spreadsheet and email it to the vendor
- Vendor tracks work in their own tool (Jira, Asana, etc.)
- You manually re-enter their updates into your system
- Nobody has a single source of truth
- Cross-org sync sends work items to the vendor’s Salesforce org
- Vendor sees tasks, logs time, and posts updates in their own org
- Changes flow back to your org automatically in real time
- One system of record. Zero double-entry.
4. Manager wants status of everything
Your VP asks: “How many items are in progress? What’s behind schedule? How much have we spent?” You open four spreadsheets and start copy-pasting into a slide deck.
- Open multiple spreadsheets and project trackers
- Copy-paste numbers into a PowerPoint or Google Slide
- Data is already stale by the time the meeting happens
- Follow-up questions require another round of research
- Open System Pulse — a live dashboard inside Salesforce
- See items by status, team member, client, and priority
- ETA engine shows projected delivery dates automatically
- Drill into any work item for full details instantly
5. Developer logs time and notes
Your developer spends 3 hours debugging an issue. They forget to log it. At the end of the week, they guess how long things took and round to the nearest hour.
- Developer tries to remember what they worked on
- Time is logged in a separate tool (or not at all)
- Notes live in Slack messages, text files, or nowhere
- Invoices are based on rough estimates
- Ghost Recorder captures time automatically in the background
- Developer adds notes directly on the work item
- Time, comments, and files all roll up to the parent record
- Accurate time data for invoicing and capacity planning
6. AI scopes the work
Someone says “We need a customer portal.” Before anyone can build it, someone has to write up what that means, break it into tasks, and estimate each one. That process alone takes a week.
- Business analyst writes a requirements doc (3–5 days)
- Dev lead reviews and creates subtasks manually
- Estimates are gut-feel numbers debated in a meeting
- Scope creep starts before the first line of code
- Type a one-line description: “Build customer portal”
- AI generates a detailed description and acceptance criteria
- AI estimates hours based on complexity and historical data
- Team reviews, adjusts, and starts building immediately
7. The Approval Trail
Developer logs 8 hours on Friday. Client sees the charge Monday morning with no context.
- Hours logged with no review process
- Client sees raw charges with no descriptions
- Disputes happen after invoices are sent
- No paper trail for who approved what
- Hours save as Draft until explicitly submitted
- Manager reviews entries in the Activity Feed
- One-click approve with full descriptions attached
- Client sees only approved hours with complete context
8. The Executive Dashboard
VP asks for project status. You spend 45 minutes pulling data from three systems into a slide deck.
- Scramble to pull data from multiple tools
- Copy-paste into slides that are stale by the meeting
- Follow-up questions require another research cycle
- No self-service option for leadership
- VP opens the portal Metrics page directly
- Pipeline breakdown and completion rates update live
- Recent activity feed shows exactly what changed and when
- Fully self-service — no analyst bottleneck
9. The Night Owl Developer
Developer works until 2am. Logs hours the next afternoon from memory. Wrong date, wrong hours, wrong work item.
- Hours reconstructed from memory the next day
- Wrong dates and rounded durations
- Notes are vague or missing entirely
- Work items misattributed across projects
- Log hours in the moment with the date picker
- Presets for common durations — no mental math
- Notes captured while the context is fresh
- Every entry tied to the correct work item automatically
10. The Client Portal Rollout
Client asks for access to see their project. You create a Salesforce license ($25/mo), set up profiles, permission sets, and page layouts.
- Purchase a Salesforce license for each client user
- Configure profiles, permission sets, and page layouts
- Train the client on Salesforce navigation
- Ongoing license cost whether they log in or not
- Client gets a magic link to the portal
- Passkey login — no passwords to manage
- Full project visibility in a clean, simple interface
- Zero Salesforce licenses required
11. The Sync Chain Debug
Something’s not syncing. You check both orgs manually, compare records, dig through logs.
- Manually compare records across two orgs
- Dig through debug logs for clues
- No visibility into what synced and what didn’t
- Hours spent on a problem that should take minutes
- Open Data Lineage on the admin home page
- See every connected org and sync health percentages
- Last sync timestamps show exactly when data flowed
- Failed records surface immediately with retry options
12. The New Install
Install the package, then spend 2 hours following a 9-step manual setup guide. Miss step 6, nothing works.
- Follow a long setup doc with manual steps
- Miss a step and spend hours debugging
- Guest user permissions are a maze of clicks
- No way to know if everything is configured correctly
- Open the Getting Started wizard after install
- Prerequisites checklist tells you exactly what’s needed
- One-click fixes for guest user permissions
- Connected and running in under 3 minutes
13. The Invoice Approval Flow
End of the month. You export hours to a spreadsheet, build an invoice in Word, email it as a PDF, then chase the client for approval over a two-week email thread.
- Export hours from your time tracker to a spreadsheet
- Build the invoice manually in Word or Google Docs
- Email the PDF and wait for a reply saying “Approved”
- Chase the client when they forget to respond
- Generate an invoice directly from approved work logs
- Client receives a portal link to review line items
- Client approves or disputes with one click — with comments
- Full lifecycle: Draft → Pending Approval → Approved → Sent → Paid
14. The Email Reply That Creates a Comment
A developer gets a notification email about a work item update. They reply directly from their inbox with a question. That reply disappears into the void — never attached to the work item, never seen by the rest of the team.
- Developer replies to a notification email with a question
- Reply goes to one person’s inbox, not the project
- PM manually copies the question into the project tool
- By the time the answer comes back, context is lost
- Developer replies to the notification email normally
- Email Inbound Handler parses the reply and creates a comment on the work item
- Attachments in the reply are linked as files automatically
- The entire team sees the comment in the activity feed — no copy-paste needed
15. The Timeline Planning Session
Sprint planning meeting. You have 25 items across three developers for the next two weeks. The Kanban board shows stages, not dates. You have no idea if the timelines overlap or if anyone is double-booked.
- Open a separate Gantt chart tool or a shared spreadsheet
- Manually enter start dates, end dates, and assignees
- No live connection to actual task status or progress
- Chart is out of date by the next morning
- Click the Timeline tab on the Delivery Hub Kanban board
- All items plotted on a horizontal date axis with color-coded stages
- Spot deadline conflicts and resource overlaps at a glance
- PM drags items to adjust dates — board and timeline stay in sync automatically
16. The Saved Filter Morning Routine
Every morning, a PM opens the board and re-selects the same four filters: their team, high priority, in-progress stages, this sprint’s items. It takes 2 minutes each time. Multiply that by 250 work days.
- Open the board and re-select assignee filter
- Re-select priority filter, status filter, date range
- Repeat every single morning across every board
- Forget one filter and miss a blocked item that needed attention yesterday
- Save the filter combination as “My Blocked Items”
- One click to load it each morning — board updates instantly
- Per-user saved filters so every team member has their own views
- Toggle Hide Empty Columns for a focused, clutter-free board
17. The Document Version Problem
You send an invoice. The client asks for a correction. You update the spreadsheet, export a new PDF, email it again. Now there are two versions floating around and nobody knows which is current.
- Generate a PDF manually and email it to the client
- Client requests a change — you edit the source file
- Export a new PDF, rename it v2, email it again
- Three versions in three inboxes — nobody knows which is final
- Generate the document from Delivery Hub — it creates Version 1
- Make corrections and regenerate — Version 2 is created automatically
- Client sees both versions in the portal with timestamps and notes
- Full version history with snapshot comparisons — no file naming chaos
18. The Contractor Portal Time Entry
Your contractor works 6 hours on Tuesday. They log it in their own spreadsheet, email it to you on Friday, and you re-enter it into your system. By then, neither of you remembers the details.
- Contractor tracks hours in their own spreadsheet or tool
- They email a summary at the end of the week
- You re-enter every line item into your billing system
- Discrepancies discovered weeks later during invoicing
- Contractor logs hours directly from the client portal
- Each entry is tied to a specific work item with notes
- Hours flow into the approval workflow immediately — no re-entry
- Both sides see the same data in real time — no reconciliation needed
19. External System Subscribes to Changes
Your finance team needs to know the moment a work item moves to “Delivered.” They want it in their ERP system automatically. You end up building a polling script that checks every 5 minutes and breaks constantly.
- Build a polling script that checks for status changes
- Script breaks silently when the API changes or times out
- Delays of 5–15 minutes between the change and the notification
- No retry logic — missed events are gone forever
- Subscribe to Salesforce Platform Events published by Delivery Hub
- External system receives real-time push notifications on every stage change
- Events include full context: work item ID, new stage, timestamp, changed-by user
- Built-in replay support — recover missed events from the last 72 hours
20. The Demo Org for Evaluation
Your team wants to evaluate a project management tool before committing. The vendor says “Schedule a demo call” and then quotes you $15,000/year.
- Fill out a contact form and wait for a sales rep to call
- Sit through a 45-minute demo that shows features you don’t need
- Request a trial — get a 14-day window with limited features
- Make a decision under time pressure with incomplete information
- Run one CCI command to spin up a fully loaded demo scratch org
- Explore every feature with realistic sample data — no time limit
- Or just install the free package directly into your own org
- No sales calls, no trials, no contracts — evaluate on your own terms
21. The Escalation That Nobody Noticed
A high-priority item has been stuck in “Blocked” for five days. Nobody noticed because the board has 80 items and the blocked one scrolled off the screen.
- Blocked items sit silently in the backlog
- Nobody checks the board often enough to catch stale items
- Client finds out the work is late before you do
- Fire drill meeting to figure out what happened
- Escalation engine detects the item has been blocked for 3+ days
- Auto-escalation bumps the priority and notifies the PM
- Attention dots on the board highlight items that need action
- SLA alerts fire before deadlines are missed — not after
22. The Weekly Client Update
Every Friday, you spend an hour writing a status email to the client. You scan the board, summarize what moved, and try to explain what’s next.
- Scan the board and take notes on what changed this week
- Write a summary email from scratch every Friday
- Miss items that moved early in the week
- Client replies with questions you could have preempted
- AI Weekly Digest auto-generates a summary of the week’s activity
- Covers items completed, items started, blockers, and upcoming work
- Review, tweak if needed, and send — 5 minutes instead of 60
- Client gets a consistent, thorough update every single week
Ready to try it?
Delivery Hub is free to install. Set it up in minutes and start tracking your team's work today.