I work with teams in the US and Europe as a freelance creative and marketing technologist, mostly remote from Copenhagen. Most projects start the same way: someone has a problem that's too specific for an agency, too urgent for a full-time hire and too important to leave on the to-do list.
If that's you, here's what I'd want you to know before you hire anyone for this kind of work, me included.
When freelance makes sense, and when it doesn't
Freelance or fractional help is a great fit when:
- You need a specific system built or fixed: a CRM migration, lead scoring, an automation stack, an AI workflow.
- You need senior judgment a few days a week, not a full-time head.
- You want someone to build it and train your team to run it, then leave.
It's a poor fit when you need someone in every meeting, or when the real problem is that nobody internally owns marketing operations. A freelancer can build you a great system. They can't be its only owner forever. If nobody on your side will run it after the project, fix that first.
Sprint, retainer or fractional
There are roughly three ways to work together, and picking the right one avoids a lot of friction.
A sprint is a fixed scope with a clear end. Two to six weeks to build a defined thing, like a scoring model or a set of workflows. Best when you know what you need.
A retainer is a set number of days a month on an ongoing list of work. Best when there's a steady stream of improvements and support.
Fractional means acting as part of your team in a lead role, a couple of days a week, with ownership of an area. Best when you need direction and execution, not just execution.
What a good first month looks like
Week one should be mostly listening. Access to the tools, conversations with the people who use them, and a look at the data. If someone proposes a solution in the first call, be a little suspicious.
By the end of week two you should have a short written plan: what's broken, what to fix first and why, and how you'll know it worked. By week four, something real should be live, even if it's small.
The one-page brief
The best projects I've done started with a one-page brief. It doesn't have to be polished. It just needs to answer:
- What's the problem, in a sentence or two?
- Who feels it most, and how much time or money does it cost now?
- What tools are involved, and who owns them?
- What would "fixed" look like in three months?
- Who on your side will own this after the project?
- Budget range and timeline.
If you can't fill in question five, that's the most useful thing the brief will tell you.
Working across time zones
Copenhagen is six hours ahead of New York and nine ahead of the West Coast. In practice that means a solid overlap in the US morning for calls, and the European afternoon for focused work while you're asleep. Many clients find they come back to finished work the next morning, which is one of the quiet perks of the setup.
If you've got a problem that fits, the form on the homepage goes straight to my inbox. Tell me what's broken and I'll tell you honestly whether I'm the right person to fix it.