A three-person studio, four kinds of work, one board
Premier Logic is a Manhattan software studio whose promise is blunt: software that pays for itself in hours returned. One developer, one designer, one marketer — each with a decade behind them, no junior layer and no account managers in between. That shape is the whole point, and it is also why their board looks nothing like an agency's.
The challenge
Premier Logic sells four quite different things at once: automation that replaces a manual weekly report, systems integration between a CRM and a warehouse, full web and mobile product builds, and ongoing growth work. Each has its own clock — three to six weeks for a first automation, six to fourteen for a product, a rolling monthly queue for a retainer — and its own definition of "what do I need to know before I start this?". With only three people and no account-management layer, anything that costs time to administer comes straight out of the time clients are paying for.
How we set it up
- ▸One board per kind of work — automation and internal tools, product builds, retainers, growth — inside a single organization, so the whole studio is visible without switching accounts.
- ▸Custom fields shaped to each: the system replaced and hours saved per week for automation; platform, branch and demo date for builds; hours used and response deadline for retainers; channel and baseline for experiments.
- ▸The backlog holds scoped-but-unstarted work, and a sprint is created from a selection of it when a two-week engagement begins — which is how the studio already sells.
- ▸Deadlines default to today and turn red when they pass, so a 24-hour brief response or a 48-hour retainer SLA is visible rather than remembered.
What it looks like now
- ✓Client work stays confidential — the board carries systems, platforms and hours rather than anything identifying.
- ✓A Friday demo is a column, not a calendar reminder: everything in "Demoed" is what gets walked through.
- ✓Retainer capacity is legible mid-month, so the queue can be re-ordered before it overruns.
- ✓Finished engagements are archived intact — comments, files and history stay attached if a client comes back a year later.
A three-person studio, four kinds of work, one board
Premier Logic is a Manhattan software studio whose promise is blunt: software that pays for itself in hours returned. One developer, one designer, one marketer — each with a decade behind them, no junior layer and no account managers in between. That shape is the whole point, and it is also why their board looks nothing like an agency's.
A two-week sprint, a three-month product build and a rolling retainer are not the same job, and a single generic task list flattens them into one. We track each kind of work with the fields it actually turns on — the branch and the demo date for a build, hours used and response time for a retainer — on one board we can see in a glance.
Studio team
Premier Logic · premierlogic.nycHOW THE STUDIO RUNS
3
senior specialists, no juniors
24h
response to a new brief
2 wks
scope to first demo
This isn't a template. The fields came out of their own process — scope in a week, design system before screens, tests carrying confidence, measurement from day one — rather than a template someone else wrote.
The studio's lead service: replacing the dashboard someone rebuilds by hand every Monday. Three to six weeks, typically — so the card carries which system it touches, what it replaces, and the hours it gives back each week.
FIELDS FOR THIS TEAM
Weekly ops report — pull straight from the warehouse
Replaces: Manual spreadsheet, ~4h/wk
Handover: Loom + written runbook
CSV importer for the billing team
System: Billing
Ops dashboard — live order status
System: CRM + warehouse
Hours saved / week: 6 (estimated)
Nightly data sync, monitored
Handover: Done — client owns the repo
↑ Switch to see the same product reshaped around a different team
More case studies
Want your board shaped like this?
Start free in a couple of minutes — or tell us how your team works and we'll set the fields up with you.
Start working on tasks →