Questions about working together

I join as a senior contributor where marketing, sales, product, data, and the systems between them have become one connected problem. I am useful when the work needs both judgment and somebody willing to build. I am not trying to take the CMO seat or become another agency to manage.

No. If the role and the work are clear, we can scope an embedded setup directly. A focused discovery is useful when the symptoms are mixed, several teams or systems are involved, or nobody agrees what should move first. It stands on its own.

Positioning, campaigns, landing pages, websites, CRM logic, audience data, tracking, reporting, sales handovers, integrations, and small internal tools. The common thread is technical B2B work with a longer sales cycle. I am not set up as a social media production team or a supplier of isolated strategy decks.

Discovery starts at 35.000 kr ex. VAT. Embedded work usually starts at 30.000 kr per month ex. VAT for one day per week. The final scope and price follow the actual problem or role.

The output follows the problem. You leave with a shared view of the current state, the main constraint, the decisions that need making, and a practical route forward. That may be a map and plan. It may also include a prototype, a repaired part of the setup, or a small tool that helps us test the next step.

The usual starting point is one reserved day per week with a three-month minimum. After that, either side can end the agreement with 30 days notice. Embedded work is invoiced monthly in advance. More time can be scoped when the work and my capacity support it.

I usually reserve one working day for the team, with enough async contact around it to keep the context moving. Some days are focused build time. Others are campaign work, decisions, reviews, or time with the people involved. The priorities can move because I already understand the team, systems, and decisions around them.

I take ownership of moving the work, but I do not disappear into a black box. I need access to the people who hold the product knowledge, operate the systems, or own the decision in front of us. Maps, decisions, implementation notes, and working methods stay with the team as we go.

I use agents for research, campaign preparation, data checks, workflow tracing, quality control, documentation, and small internal tools. They hold more of the working context and make repeatable checks easier to run. I remain responsible for access, priorities, business judgment, and the final output. Sensitive material follows the setup agreed for that client.

I read it myself and reply by email. If the situation looks like a fit, the next step is usually a short call to understand the context and decide what needs scoping. If it is useful to continue, I send a proposal with the role or problem, timing, price, access, and expected output. The inquiry and fit call do not cost anything.

Enough context to understand what is stuck, the decisions involved, and any real deadline or constraint. Once the work starts, I may need time with the people closest to it and access to the relevant systems, data, and existing material. I request only what the work needs. I sign standard NDAs and agree the data setup with the client.

Both. I am based in Denmark, and remote work is normal. On-site time is useful when the work needs a room, a whiteboard, or direct time with the team. Start timing depends on my current capacity and the access the work needs. The proposal sets the date and working rhythm.

That is normal. Send the messy version. I can tell you whether it sounds like focused discovery, an embedded role, or somebody else.