Why I no longer respond to 'Let's do something together' - and what works instead

"Let's do something together!" - I regularly receive this message via various channels. Sometimes it's an email, sometimes an Instagram DM or a comment under one of my videos. As someone who is generally open to collaborations, I usually reply in a friendly manner with: "Sure, I'd love to! What do you have in mind?"

And then... nothing. Radio silence. The person who just enthusiastically suggested a collaboration doesn't get back to me. This pattern has repeated itself so often in recent years that I decided to get to the bottom of this phenomenon and explain to you why such vague requests come to nothing - and how you can do better if you really want to work with me.

I am convinced that there is a better way for successful collaborations that benefit both sides. In this article, you'll find out what's important.

The pattern behind vague requests

Do you know this too? You get a message like "Hey, do you want to do a podcast together?" or "I'd love to do a YouTube collab with you!". That sounds interesting to me at first - after all, I like exchanging ideas with others from the TYPO3 community.

The pattern usually goes like this:

1. I receive a vague request without a concrete idea
2. I ask: "What exactly do you have in mind?"
3. The other party no longer responds or responds very late
4. If an answer comes at all, it is usually just as vague as the first message

On reflection, this phenomenon is not so surprising. Behind many of these requests is probably the following thought: "Wolfgang has reach/expertise/a network - if I do something with him, I'll benefit from it." In itself, this is completely legitimate! Collaborations thrive on both sides contributing and gaining something.

The problem starts when the person making the request expects me to do the conceptual work. They throw a vague idea into the room and secretly hope that I will now pick up the ball, develop a concrete concept and take over the organization.

This is unsatisfactory for both sides: the person making the inquiry doesn't get a positive response and I waste time with inquiries that lead nowhere.

What these requests overlook: Genuine collaborations need more than just a spontaneous impulse. They require planning, mutual respect and, above all, a clear idea that offers added value to both sides.

My time as a valuable resource

I have been working intensively with TYPO3 since 2006. During this time, I have produced hundreds of video tutorials, led workshops, set up a community forum and become part of the TYPO3 Education Committee. This experience and the resulting knowledge are my most important assets.

There are only 24 hours in a day. Besides existing projects, client meetings, producing new content and updating courses for new TYPO3 versions, there's not much time to spare. Every hour I invest has to be put to good use.

When I receive a vague request, I'm faced with the decision: should I take the time to develop a concept for someone else? Time that I could otherwise invest in my own projects or in my existing community?

That may sound harsh, but it's a reality that we all face: Time is our most valuable and scarcest resource. Giving it away - and this is exactly what happens when I take on concept work for others without it being clear whether anything will come of it - is simply not sustainable.

Don't get me wrong: I like to help, share my knowledge and support others. My YouTube videos, my forum and my courses are there to do just that. But cooperation is something else. It requires a commitment from both sides - and that also means that the person making the request has given it some thought and has a clear idea.

The two key questions behind every collaboration

I ask myself two fundamental questions about every potential collaboration - and it is precisely these questions that every cooperation request should answer from the outset:

Question 1: "What exactly should be created?"

This question is aimed at the specific end product. Is it about:

• A joint tutorial video on a specific TYPO3 topic?
• A podcast episode about specific challenges in TYPO3 integration?
• A joint workshop for a defined target group?
• A guest article in my newsletter on a specific topic?

The more concrete this idea is, the better I can assess whether it fits into my planning and whether I can find the necessary resources for it. A vague "let's do something together" doesn't give me anything to work with.

Question 2: "What's in it for both sides?"

This is about mutual benefit. Good cooperation is characterized by the fact that both partners benefit. This doesn't always have to be financial - it can also be about reach, knowledge transfer or access to a new target group.

So I ask myself: What is the benefit for me? Am I contributing my time and expertise in order to...

• gain new users for my services?
• deepen my knowledge in an area?
• increase my profile in a certain segment?
• simply have fun with an exciting project?

And at the same time: What is the benefit for the other side? Is it transparent why they want to work with me?

A good cooperation request should answer these two questions of its own accord - ideally in such concrete terms that I can immediately see whether the project makes sense for both sides. If I have to ask what the goal is in the first place, the collaboration starts with an imbalance.

What a good cooperation request looks like

Now that we've discussed the problems with vague requests, I'd like to show you what a really good cooperation request might look like. Here is a fictitious example that contains all the important elements:

---

Subject: Proposal for joint tutorial video on TYPO3 v13 Site Sets

Hi Wolfgang,

I've been following your TYPO3 tutorials for over a year and especially appreciate your clear way of explaining complex topics. On my channel (link) I mainly deal with frontend development and TYPO3 extensions.

My concrete proposal: I would like to create an approx. 30-minute tutorial video with you on the topic "Migration from TypoScript-based configuration to new site sets in TYPO3 v13".

The concept:

• You explain the backend perspective and the basic concept (approx. 10 min)
• I show the practical implementation using a real example (approx. 15 min)
• Joint Q&A on typical pitfalls (approx. 5 min)

What you would get out of it:

• Expansion of your content library with a practical migration tutorial
• Access to my community of approx. 3,000 TYPO3 developers who mainly work with extensions
• A finished video for your channel (we could publish it on both channels)

What I would get out of it:

• The chance to work with an experienced TYPO3 expert
• More attention for my channel through the collaboration
• In-depth knowledge of the backend perspective of the site sets

I could take over the technical part (recording, editing). I would be flexible in terms of time - next month if that suits you.

What do you think of this proposal? I look forward to your feedback!

Best regards, [name]

---

What makes this request so good?

1. It's concrete: it's about a specific topic, format and a clear timeframe.
2. It shows preparation: the enquirer has looked into my work and chosen a topic that matches my expertise.
3. It outlines the added value for both sides: It clearly states what everyone will gain from the collaboration.
4. She makes a clear proposal for the division of labor: not only is the idea presented, but also who could do what.
5. She respects my time: the effort is kept manageable and realistically estimated.

With such a request, I would immediately recognize whether the project fits into my planning and whether it is interesting for me. This significantly increases the likelihood that I will respond positively - even if I had to decline due to time constraints, I would probably make alternative suggestions or want to stay in touch in the future.

Practical tips for potential cooperation partners

If you would like to work with me now, I can provide you with a small checklist. These tips will help you to formulate a request that hits the mark:

Checklist for your cooperation request:

1. Name a specific topic What exactly should the collaboration deal with? The more specific, the better. "TYPO3 extensions" is too vague, "integration of payment extensions in TYPO3 stores" is much more specific.
2. Define the format Is it a video, an article, a podcast, a workshop? How long should it be? Where should it be published?
3. Explain the added value for both sides What is your own benefit? And above all: What do you think my benefit could be? Be honest and realistic here.
4. Show your own expertise What are you good at? What can you contribute? A reference to previous work helps me to assess you.
5. Make a proposal for the division of labor Who will take on which aspects of the project? There should be a recognizable balance here.
6. Outline a time frame When could the project start and when should it be completed?

Before making contact:

Before you send your request, take time for these preliminary considerations:

• Know my work: watch some of my videos, read my newsletter or visit my forum. This will help you recognize topics that interest me.
• Check the relevance: Is your proposal interesting for my target group (TYPO3 developers, integrators, agencies)?
• Be realistic: A request for a 90-minute live webinar requires a lot of preparation. Perhaps start with a more manageable project.
• Offer real added value: Think about what you can contribute that is truly unique. This could be specialist knowledge, but also a certain perspective or access to an interesting target group.

How you stand out:

Most collaboration requests I receive are vague and impersonal. With these tips, you are guaranteed to stand out:

• Personalize your request (no standard texts)
• Refer to specific content from me that has inspired you
• Make it clear that you have really put some thought into it
• Be authentic - I prefer to work with real people rather than perfectly optimized marketing personalities

By the way, there is no perfect timing for a request. But the better prepared it is, the more likely it is to be answered positively - even if I have a lot to do at the moment.

My invitation to you

After all these "rules", I would like to make one thing very clear: I am very open to exciting collaborations! I don't want to scare anyone off with this article, but rather pave the way for collaborations that work really well and bring joy to both sides.

I find collaborations in these areas particularly interesting:

• Joint tutorials on new TYPO3 features: especially with the transition to TYPO3 v13, there are many exciting aspects that we could shed light on together.
• Interviews with TYPO3 experts: Do you have a special perspective or specialized knowledge? An exchange in interview form could be valuable for many.
• Practical projects with concrete benefits: You have an idea for a tool, an extension or a method that makes work easier for TYPO3 developers? Let's talk about it!
• Cross-platform content: Are you active on platforms that I don't use yet and would like to share TYPO3 knowledge there? That could be interesting.

The ideal first contact looks like this for me:

1. An e-mail or a message via my contact form
2. A short but concrete concept based on the tips above
3. A link to your previous work so that I can get an impression of you

You don't have to deliver a perfectly prepared presentation. It's enough for me to see that you've put some thought into it and have a clear idea.

What I particularly appreciate: People who are authentic, bring in their own expertise and actually want to make a difference - be it in the TYPO3 community or in web development in general.

Your ideas are welcome - with the right preparation

I hope this article has given you a clear insight into why I hardly ever respond to vague "let's do something together" requests - and at the same time shown you what a good cooperation request can look like.

I'm not interested in putting up barriers or appearing unapproachable. On the contrary: I am happy about every well thought-out request and every concrete suggestion. Such requests show me that you value my time and expertise and are willing to contribute something to the potential collaboration yourself.

The best collaborations happen when both sides have a clear idea of what they want to achieve and what they can contribute. They don't start with vague ideas, but with concrete suggestions that make you think and want to work together.

So don't be afraid to approach me! Simply prepare yourself well, bring a concrete idea with you and think about what we could both gain from working together. With this approach, there is a good chance that the request will result in an exciting joint project that will ultimately benefit not only us, but also the TYPO3 community.

I look forward to your ideas!

Back