Social Media Management
A feed with a point of view.
Strategy, calendar and production in one loop. Because the edit suite is down the hall, a shoot becomes thirty pieces of content instead of one — and we report on what moved, not on impressions.
A recording rhythm you can actually sustain
How we think about it
Strategy and production usually sit in different companies, which is why so much social output is expensive and generic. Here they are one loop: what we learn this week changes what gets shot next week, and a single shoot day is planned from the start to yield a month of material.
Sharing a building with the edit suite is the whole economic argument: one shoot day becomes a month of content instead of a single hero film. Paid amplification runs through the same Digital Marketing budget and reporting, so a post's performance and its promotion are never two separate stories.
What this covers
The work, specifically.
- 01
Content strategy
A position worth holding and a calendar that survives a busy month.
- 02
Short-form
Vertical video cut for each platform's grammar, not one export posted everywhere.
- 03
Community
Replies and conversation treated as part of the work, not overflow.
- 04
Paid social
Promotion behind the pieces that already earned attention organically.
- 05
Analytics
Reporting on what moved — saves, replies, signups — rather than impressions.
Need Social Media Management for something specific?
Tell us what you're trying to ship and we'll say plainly whether this is the right service for it — including when the answer is no.
How it runs
The same four steps, whatever we're building.
No account-manager relay. The lead on your project is someone who builds, and they stay on it from the first call to the last deploy.
Scope
A week of hard questions. We map what you actually need and say plainly which parts we'd cut.
Prototype
Something real in front of you early, not a document about it. Opinions get cheaper.
Build
Two-week cycles, a demo at the end of each. You see progress, not status reports.
Hand over
Documentation, a walkthrough, and the keys. Support if you want it — never as a hostage.
Questions
The things people ask before they enquire.
We write, shoot, edit and schedule. Handing a client an empty calendar to fill is not a service.
A cadence you can actually sustain after we hand over, agreed up front. A schedule that collapses the month we leave was the wrong schedule.
It depends on scope, but we will give you a number before you commit to anything. Most engagements start with a paid discovery — a fixed fee, a week or two — which ends in a written scope and a real budget. If the budget does not work, you leave with the scope document and no obligation to continue.
A typical first ship is around six weeks. Larger builds run in two-week cycles after that, each ending in a demo of something that actually runs. You will know within the first cycle whether the timeline is holding, rather than finding out near the deadline.
The people you meet. The lead on your project is someone who builds, and they stay on it from the first call to the last deploy. There is no account manager relaying messages between you and an unseen team.
You own everything — code, assets, accounts, domains. We hand over with documentation and a walkthrough, and your team can run it without calling us. If you would rather we stayed on for maintenance or a next phase, that is a separate agreement, not something buried in the original contract.
Yes. Most of our work is remote, and we keep a few hours of overlap with your working day for calls. Timezone has not been the hard part; unclear scope has.
Where it meets the others