Case study · Client build
Operations & workflow automationWhen a project is done, accounting already has what it needs.
Airtable systems that helped a growing agency scale its team without scaling the chaos.
Mass Inbound was scaling fast and moving into a pod-based team structure — but their project management and billing processes were still built for one person. We rebuilt both from the ground up in Airtable, connecting delivery to billing with zero manual handoff, so the team has a shared way to run the work and new hires have clear processes from day one.
- Airtable
- Project Management
- Billing Automation
- Pod Workflows
- Process Documentation
- Team Scaling
Client

A data-driven digital marketing agency scaling its team into a pod structure — and needing the systems to match their growth.
- Airtable bases built
- 2
- Back-and-forth
- ↓
- Billing clarity
- ↑
- Implementation
- 4mo
Ken Massa — Owner, Mass Inbound
Client testimonial
“A lot of the things that we have done over the last four months have been very beneficial for the new hires and for our processes — because as we scale, what I was doing before would just never work with how a team works, especially in a pod structure.”
Ken Massa
Owner, Mass Inbound
Ken came in knowing his processes needed to change — but needed a partner who understood both the systems side and the human side of scaling a team. Over four months of iterative implementation, we built, tested, broke, and rebuilt — until the system genuinely fit how his team worked. That's the difference between a tool someone shows you and a system someone builds with you.
01 / The challenge
Processes built for one person can't scale a team.
A growing agency. A pod structure. Systems that hadn't kept up.
As Mass Inbound grew and transitioned into a pod-based team structure, the project management and workflow processes that worked for a single operator started breaking down. Without the right systems, scaling the team meant scaling the chaos — new hires had no clear processes to follow, and the handoff from project completion to billing was fragmented, manual, and slow.
The accounting team was caught in a loop of back-and-forth communication just to get the information they needed to invoice clients. Operational clarity was suffering — and it was only going to get worse as the team grew.
The question behind the brief
How does completed work become a clear handoff, without someone having to reconstruct the details?
Before
- Project management processes built for a solo operator — not a team
- No structured onboarding system for new hires in a pod structure
- Manual, fragmented handoff from project completion to billing
- Constant back-and-forth between teams to gather invoicing information
- Operational clarity suffering as the team scaled
After
- Airtable project management system built for team and pod workflows
- Clear, documented processes new hires could follow from day one
- Automated billing handoff — project completion triggers seamless data transfer
- Accounting team receives everything they need without chasing it down
- Systems that evolve with the business as it continues to grow
02 / What we built
Two Airtable bases. One seamless operation.
Strategy, simplicity, and systems that evolve with your team.
Rather than a surface-level fix, we built a connected architecture — a primary project management base designed around how teams actually work in pods, paired with a dedicated automation layer that bridged the gap between delivery and billing.
- 01
Airtable Project Management Base
A fully structured project management system rebuilt from the ground up for pod-based team operations — with clear task ownership, status tracking, and process documentation that new hires could follow from day one.
- The problem it removed
- Processes built for one person, with no clear steps for new hires.
- What they can do now
- Every pod works from a shared structure that new hires can follow from day one.
- 02
Automated Billing Handoff Base
A secondary Airtable base purpose-built to automate the transition from project completion to billing — capturing all required data and transferring it directly to the accounting team without manual intervention or follow-up communication.
- The problem it removed
- Accounting going back to the delivery team for the details it needed to invoice.
- What they can do now
- Accounting gets the project information it needs for billing when the work is completed.
- 03
Cross-Base Automation & Integration
The two bases were connected via automation workflows — so that actions in the project management base triggered the right outputs in the billing base, creating a seamless, end-to-end operational flow with no gaps in between.
- The problem it removed
- Someone having to pass the information from delivery to billing by hand.
- What they can do now
- Completing a project triggers the next step in billing automatically.
- 04
Team Process Documentation & Evolution
Systems were built to be malleable — not rigid. The team was given space to test processes, surface gaps, and rebuild where needed. Over four months, the system evolved iteratively alongside the team's real-world usage.
- The problem it removed
- A rigid system the team would have to work around.
- What they can do now
- The team can test, find gaps, and improve its processes as it grows.
- 01
Project work
Task ownership, statuses, and process information in the project management base.
- 02
Project completion
Cross-base automation passes the required project information to the billing base.
- 03
Accounting handoff
The accounting team receives the information it needs for billing.
Your team
Is your team growing, but still chasing the details?
Mass Inbound’s accounting team stopped chasing project details once the handoff was built into the workflow. If your team is growing and the same questions keep coming up, that’s where we start.
Tell us where the work slows down. You don’t need to know which tools to use; we start with the process.
03 / The outcome
Operational clarity. Zero back-and-forth. A team that can scale.
The systems now grow with the business.
The implementation delivered a meaningful shift in how Mass Inbound operated day-to-day — not just a new tool, but a new way of working that the whole team could follow, repeat, and build on.
Workflow efficiency
Groundbreaking improvement in how the team manages projects — built for pods, not solo operators.
Billing back-and-forth
Seamless automated transfer of project data to accounting — no chasing, no gaps, no delays.
Team scalability
New hires onboard into clear processes. The system evolves as the team grows — by design.
The takeaway
A handoff is a workflow worth designing.
The useful connection in this project was between the people delivering the work and the people who needed its details next.
If accounting, operations, or another team has to chase information when work changes hands, map what triggers the handoff, what data is required, and who needs to act. That can be a focused starting point for a systems project; the tools and scope follow your process and the team that will use it.
How custom systems projects workIf you’re considering something similar
A little more context.
Want your team to grow without the back-and-forth?
Strategy. Simplicity. Soul.
Let’s map out the systems your whole team can run on, so the business can scale without the operational chaos.
A conversation about your operation
Where does your team keep chasing the details?
Tell us which handoff slows the work down, who needs the information, and where it lives today. We’ll review the workflow and reply with a useful next step.
You don’t need to know which tools to use. Start with the process that needs attention; scope follows discovery and a written plan.
Explore more client stories