Development partner

Development Partner for Communications Agencies

Communications agencies shape the message, the channel, and the strategy. I build the platform that carries it — from editorial platforms to membership sites, intranets, and integrations with the client's systems. Based in Kalmar with a focus on Sweden; Nordic and international engagements work just as well — several projects are delivered in English.

External developer for communications agencies

Communications agencies shape the message, the channel and the strategy. As an external developer and consultant developer Pihlfelt builds the platform that carries it — from editorial platforms and membership sites to intranets and integrations with the client's business systems.

Concrete assignments

  • Editorial platforms for organisations with multiple audiences.
  • Membership sites with integration to member registers and payments.
  • Intranets with single sign-on and access control.
  • Migration of editorial content between CMS without losing SEO.
  • Technical reviews and remediation when taking over existing engagements.

Long-term technical responsibility

For communications agencies, technical continuity is often more important than individual projects. Pihlfelt takes long-term technical responsibility — planned maintenance, security updates and continued development after launch. This means you can offer the client a complete engagement, including the technology, without committing to a full-time hire.

How the collaboration works

Clear roles: you drive the client project and own the content and communication, I take technical responsibility. Structured handover when taking over an existing engagement. White-label or openly disclosed — your choice per client.

Based in Kalmar, partnerships with communications agencies across Sweden.

When

When the agency needs me

01

When the client needs an editorial platform that actually scales.

02

When an internal channel or membership site must be built from scratch.

03

When integrations with the client's business system or member register are required.

04

When the existing site needs to be rebuilt without losing content or SEO.

05

When you need a developer who can take long-term technical responsibility.

How

How the collaboration works

01

You drive the client project — I am the technical part of the team.

02

Clear roles: you toward the client, me toward the code.

03

Structured handover if I take over an existing technical commitment.

04

Long-term support and continued development after launch.

05

Transparent communication about time estimates and technical risks.

Examples

Example assignments

  • Editorial platform for an organization with multiple audiences.
  • Membership site with integration to member register and payments.
  • Intranet with single sign-on and access control.
  • Migration of editorial content between CMS platforms.
  • Technical review and remediation when taking over an existing engagement.

Questions & answers

Frequently Asked Questions

Common situations where the agency reaches out: • A client project requires more technical capability than in-house resources allow. • You have won an engagement but have no developer to take technical responsibility. • A campaign needs a custom technical solution on short notice. • An existing project is stuck or needs to be taken over from a previous developer. • You want to be able to sell tech-heavy engagements without hiring. Both project-based and ongoing collaborations work.
Most often, the agency project lead and I talk directly — without multiple intermediaries. The process: 1. You briefly describe what the client needs. 2. I come back with a time and cost estimate. 3. Once you approve, work starts with continuous check-ins. 4. Delivery to you, either for onward delivery to the client or directly to the client under your name. I work both white-label and openly — your choice.
An external developer is often the right choice when: • The need is too small or irregular for a full-time hire. • You already have a technical team but need extra capacity for a period. • A specific skill is missing in-house — e.g. WooCommerce, Laravel, AI integrations or complex APIs. • You want to be able to take on engagements you would otherwise have to decline. • You want to test a technical collaboration before potentially hiring. For many agencies, an ongoing relationship with an external developer is more cost-effective than a hire — you only pay for what you actually need.
You do. Always. I am a technical supplier to you, not to the end client. That means I don't contact your client without your knowledge, and you control how I am presented — as an external partner, as part of the agency team, or completely anonymously.
Two common models: • Fixed price per assignment, based on an estimate before we start. Good for well-defined projects. • Ongoing hourly billing, with a monthly cap. Good for continuing partnerships where scope varies. Agency pricing is negotiated separately from individual consulting engagements — we find a level that works for both parties over time.
Yes. I deliver the technology, you deliver to the client. Email conversations, documentation and deliveries can be branded as yours. If you prefer that I am openly part of the team in the client dialogue, that also works — it's your choice per project.

Discuss a partnership?

Get in touch. Based in Kalmar, working with agencies across Sweden.

Contact Us