Case StudyCross-channel engagement, built faster
How BAC helped Iterable's marketing team ship faster, scale smarter, and build real engineering culture — without the overhead of permanent hires.
Move fast without breaking the bank
The Iterable marketing department needed to increase the speed at which they develop and iterate on their marketing website in order to achieve key company growth metrics.
They also needed the flexibility to change directions quickly and increase or decrease team output as needed. Hiring in house is a lot of investment, slow and difficult to quickly scale up and down.
Therefore they engaged with BAC to bring needed expertise and resources quickly.
Enhance & Augment Team — NOT “Over the Fence”
At BAC we try to avoid the traditional “over the fence” agency development model. In an ideal engagement we quickly learn what internal resources a team has and what its upcoming objectives are and then augment the team with additional experts: devs, designers, PMs as appropriate.
From there, the team (both BAC and client) work together to quickly and iteratively achieve objectives.
Initial internal team
+ BAC developer & architect
+ 2nd developer & designer
Results
Faster iteration and flexibility
Better communication
More learning
Best Practices — SDLC & CI/CD
In order to work together effectively, especially when team members are in different time zones, we need a set of lightweight team processes. Each team is different so we start each engagement by tailoring a team process selecting from our experience of best practices.
Iterable's internal marketing dev team was new and small and therefore had very little process in place so within the first week of the engagement we worked together to design and implement a SDLC and CI/CD pipeline.
Scrum Process
Project Tracking
Asana for visibility and accountability
Daily Standup
15 min — updates, blockers, quick syncs
Biweekly Sprint
Planning + retro — improve and plan ahead
Git Branching & CI/CD Pipeline
We set up buddy.works pipelines so branches automatically deployed to corresponding environments. Developers push → auto-deploy → review → merge → release.
What changed
Quick feedback and faster release cycle
Safer releases and less bugs
More flexibility to change work
Predictable work and streamlined communication
Learning from feedback and code reviews
Easy to add/remove additional resources to team
Ready to work like this?
Whether you need to augment your team, build process from scratch, or ship faster — we're ready to help.