Skip to main content

· 5 min read
Tim Post

The point of an early design partnership period is to match everything your product is capable of doing with what the current market needs it to do in order to achive fit. Right now, early software startups really seem to need turn-key documentation sites that someone else hosts and updates for them, so that's precisely what we're putting into the first product that we've actually developed in conjunction with early clients.

We can now deliver a fully-responsive developer documentation & community site with the following features:

  • Automatically updated by us! We manage content updates, release notes, screen shots, feature spotlights and feeds. You schedule releases on a shared calendar and push a button to make it live when you're ready. We handle updating your documentation and writing the release notes automatically!

  • We can pull tickets that you tag for us in your existing issue tracking software to help us build narratives around releases. Just tag them for-echoreply along with major item or minor item respectively and we'll use them as building blocks in the story. We don't require many face-to-face calls.

  • Built on Docusaurus to bring the flexibility of MDX and fully-responsive / accessible design that is easy to customize to match your brand. We'll handle the initial theme setup to blend with your site. Anyone that knows Markdown can edit content; advanced users can use MDX and react components.

  • We store your video content on IPFS through Filebase. No more cluttering git repositories with mp4 files, or uploading videos to YouTube (unless you want to!). Additionally, Filebase provides true distributed storage via IPFS; while it provides an Amazon compatability layer in the form of an S3 compatable API, your files are actually hosted around the globe and pinned on the real IPFS.

  • Static content is built and Hosted on Netlify with serverless functions enabled for richer content experiences, metrics, live support and others. We're actively developing more Docusaurus plugins that take advantage of serverless functions, which is outside of the realm of the goals of the project itself.

  • Organized so that all of your content is stored separately from code, in plain text files. Anyone with knowledge of Markdown can create, edit and translate content or send pull requests to improve it, but your functions, components, configuration, etc is stored in a private repository. We accomplish this through Git submodule orchestration.

  • We submit PRs in advance of release dates and collaborate around it just like you currently do code, so you always know in advance what's going to be published.

Pricing for this depends on your release cycle, and the complexity of your software. To make sure the product works well for everyone, the base price includes having us involved in all of your releases, even minor ones, so that we remain involved in the release narrative. We'll make a bigger production out of the ones where there's more to get excited about.

If you're interested in this, please reach out to us so we can assess your product and see if we'd be a good fit at this stage. We can support monthly or longer release cycles with very little lead-in time and be up and running smoothly within 45 days.

Does it have to be (Docusaurus / Filebase / Netlify / etc)?

For now, in most cases, yes. Gatsby is another option if Docusaurus won't fit the bill.

This arrangement lets us automate (for the most part) both the incoming end and delivery end of the work. However, it's feasible that we could do things a little differently - reach out to us if you have something else in mind and we'll see how it might fit in our workflow.

Can you migrate our existing documentation site?

In many cases, yes. It would depend on the volume of content, the amount of content with proprietary markup, internationalization strategy and design. We'll apply your logo and brand theme colors when we get started.

How do you coordinate everything?

We use a shared calendar (Google) as well as a shared Slack or Discord channel; for the most part we'll feel like a part time remote employee.

Who writes the content?

The person with the most experience in your domain (who also naturally knows what to look for) will put together the foundation for the content. For consistency, only one or two editors (max) at a time work on the final product that we commit, so that voice and tone stay the same and writing standards remain above objectively met.

How much is it?

The base price is $2500.00 Monthly and includes two feature screencast videos and up to 10 pages of documentation professionally written or updated each month.


A 45 Minute Introductory Call Is Free - Take Advantage Of It With No Obligation! →

The initial evaluation is free and there's no pesky sales follow up calls. If we don't get excited about working togther on the call, we won't pester you.

· 5 min read
Tim Post

Ultimately, you'll agree that capturing traffic from search even when the user's intent is pretty clearly not to land on a marketing page is something that you need to do.

But, you need to do it in a way that makes the Internet at least not worse in the process. If you haven't yet been down the early-devtool-startup rabbit hole, this is usually something that founders struggle with after realizing that shares from thought pieces just aren't producing enough qualified leads. Nobody, especially people on the engineering teams, likes seeing word salad on the company blog.

If you take nothing else away from this, it's that you should trust that instinct whole-heartedly. First, littering is bad, even on the Internet. You don't want to take someone that's already in the throes of anxiety because they're searching for whatever it is you're trying to capture, and you're doing it with the intent of showing them something that is .. probably very unlikely to help them in the moment. That's not a great first impression and why are you making people's days worse anyway?

SEO Content must first, above all else, add value to the endeavor that you're capturing.

If someone is running as fast as they can down a hallway with a mouth full of half-eaten habanero peppers while yelling for something to drink, alcohol probably isn't helpful even if it eventually kills the pain.

If you're going to put yourself between a person and the information that they really wanted to begin with, try your best to give them that information as an early part of your process. A tactic we're seeing increasingly used by other content marketers is trying to get search traffic for particular errors and then dropping someone into a webinar instead. This isn't technically bait-and-switch if you want to rules-lawyer it, but it doesn't stand up to a lot of scrutiny either.

The best strategy is to pick opportunities where you naturally fit the solution.

Do you need to get search traffic for something that has literally hundreds of duplicate questions on Stack Overflow about exception handling, because you make that particular pain go away in, say, Python or Java?

Great. Go sort through those questions, find the best one that you can along with the best answer. Let your visitors know that you looked through the questions, found the best information and then give them links. Then bring your own experience to the table and make it convenient for the visitor to fall into your funnel when they have more time.

And then tell them why using your product means not wasting any more time of their life wading through landing pages just like this one.

You optimized for their time this way by:

  • Doing their research for them.
  • Giving them what's probably the best answer they can find.
  • Explalining why right now is actually a good time to tell people about the product, and ideally giving them. some means of rediscovering it later (retargeting is evil here, be careful).
  • Being deliberately transparent to save some cognitive overhead.

Don't try to force content that doesn't want to be created.

Don't force this or it won't work. If it feels like you're writing a word salad, stop until something leads you to discover a way to write it that also feels genuine and good. Bad marketing content can do more to damage your overall perception because it tends to age very poorly in places that people forget all about, but still gets traffic.

If what you're writing starts off as bad, it has nowhere to go but terrible as it ages. You don't want that for the sake of chasing SEO and content KPIs that are mostly arbitrary anyway!

But that doesn't mean you can't sell and promote yourself!

You need to be respectful of your visitors' time, we didn't say anything about humble. You now have the real position of having provided something of actual value, so be bold with your pitch and be sure to remember that folks tend to be very impressionable right after getting help.

These are a great place to provide incentive to follow social accounts to get something else of value, say an extended freemium package or beta period, or something else that's convenient for them to claim when they have more time to get distracted.

Concluding ...

You can meet content marketing goals and still feel good about yourself as a writer; you just have to do it creatively. Writing killer canonical resources for common problems is one way to do this, but just one of many. As long as you at least make the user feel like finding you moved them in the right direction, these pieces can bring in a steady stream of curious adopters. Just make sure you keep track of them, keep them up to date, and keep them real.

A 45 Minute Introductory Call Is Free - Take Advantage Of It With No Obligation! →

The initial evaluation is free and there's no pesky sales follow up calls. If we don't get excited about working togther on the call, we won't pester you.

· 7 min read
Tim Post

What did you envision happening once everyone found out what you were working on and could actually touch and interact with it? Did you try not to think about that and let your creativity take it wherever it was destined to go, or did you think about what it would be like to see people use and appreciate your work? It's probably different for everyone, but I think we all remember it as one of 'the' experiences in our catalog of emotional explosions from owning an early-stage company.

The trouble is, you probably had no idea how difficult it would be to take the leap from the 14 people you know finding out about your product to just one person you don't know finding it through your initial marketing efforts. In fact you might have felt slightly terrified at just how hard it can be to get unpaid user acquisition funnels actually primed and working. Notice that I didn't say how expensive, because that's not even a luxury most could realistically contemplate at that point. We're talking baby steps in anything that isn't directly pushing the product, and that often includes marketing.

Co-marketing partnerships are an extremely attractive option at this point for the following reasons:

  • They often cost little in terms of time and money initially because they're easy to cost-box; we'll get into that soon.

  • They have a higher-than-average probability of over-performing compared with other low-cost efforts that only require some content being published and promoted organically in some way. One successful pilot could net more qualified users in your funnel than weeks of trolling landing pages around your own networks.

  • They hinge on networking early which is critical. The sooner you start making friends that know you primarily because of your business the better.

Co-marketing schemes take many forms; the essential ingredients are people putting up equal sweat and financial stake in order to produce something greater than the sum of what they could do with it alone.

Main Developer Co-Marketing Opportunities

Co-marketing for Developers falls into three general buckets:
Co-branding is where you and another party organize a joint offering or event that you'll contribute equally to producing and marketing. You have a product and some resources to promote the arrangement, and the other party brings their customers or followers to the table.

This isn't an exhaustive list of co-branding shenanigans like the one that you copied from the board in marketing school; this is a list of stuff that is most accessible and repeatable to early-stage companies.

Co-Branded Co-Marketing Wins Most For Technology Startups

Out of all three, we recommend the co-branded approach to companies at the seed phase. These have the lowest overall cost and lowest initial cost which is crucial, and the resulting marketing tends to be authentic and well-received. Since the partner marketer also has some sweat-equity in the game, these campaigns tend to run smoothly since both parties remain attentive and responsive as long as they continue to produce.

If you have outside capital, then you have a few thousand bucks you can pony up to a joint marketing pool, or you have that $500 advertising credit you got from someone through the process of signing up for all the crap you need initially. If you're going to throw precious resources at anything marketing related very early when things are scarce, use this approach if you can.

Likewise, if you just want to build a fantastic network of friendly companies and help eachother with growth hacking, jump in!

Just treat them as paid enodorsements. Have the endorser specifically say "Hey this company caught my eye and I think this thing they make is very relevant to all of you" and make sure they can speak as passionately as you can about it, and you're set.

This means your product needs to solve some kind of pain for them, and they need to be really excited about that. If you don't have this chemistry, don't waste your money. It won't work.

With this route, you have some influence over the messaging, you can be there as they use the product so you can help them get the correct experience if bugs pop up (and get them fixed before you air the campaign), and you can plan supporting messaging and distribution ahead of time because you know when it'll be published.

This is our second favorite route only because it costs more, but you're the only one who risks not getting anything out of it. It's better to do this with stronger hunches that can have big payoffs.

Blind Reviews Are For Adolescent Product Teams

You need honest product feedback from as diverse a group as possible, and you need organic links, and you need blogs talking about you, and maybe by now you can afford some $50 Amazon gift cards?

Then you're ready to offer a review partner program! It's a very one-sided arrangement where the people trying your product control everything; you just provide them with access and motivation.

What You Do / ProvideWhat They Do / Provide
Software licenses & access, motivation, agreement and hands-off support.An honest review linking to your site, promoted to the community along with constructive feedback.

Depending on who you invite, this can get you a lot of great feedback and exposure, as well as expose lots of issues that would have been an inconvenience to a great many more people had you not done the testing. When we do this, our goal is to get feedback like "this was a pain to come back to after I was done feeding the baby" and not just "wow, dark mode!", so organize it responsibly and mindfully.

This becomes a great option in the months leading to your product becoming generally available.

Conclusion

Co-marketing is one of the VERY first things you want to get good at seeking and coordinating when you need to get something new in front of people that are likely to care about it. Schemes where a partner not only increases the resources that can be put into it, but also carries half the load, are the most ideal for the early days.

In tha later days, it's great practice to pump goodwill back into the community you hope to serve by offering deals to key influecers in respectful, non-exploitative terms without oppressive restrictions. This isn't scary, it's just the process of moving your product from almost ready to ready. You need to understand how its going to impact people before it does, and this is a great way to find out.

And, we can totally help with that.


A 45 Minute Introductory Call Is Free - Take Advantage Of It With No Obligation! →

The initial evaluation is free and there's no pesky sales follow up calls. If we don't get excited about working togther on the call, we won't pester you.

· 4 min read
Tim Post

We pay marketers to come up with landing pages that resonate with developers, and those marketers ultimately pay the very developers they're hoping to entice to build the page .... doesn't that sound a little bit weird to you?

MDX means better marketing. If you take nothing else away from this, make sure that you look into putting MDX/JSX in the hands of your marketing team, so that they can form and bake their own clay in the kilns. Pages that marketers can produce themselves, with no other gate keepers, are going to convert better and faster than anything else.

Why is this?

  • Because your marketing team can make mistakes faster, learn from them, and iterate in multiple directions at once. You're freed when the prospect of possibly wasting someone else's time is off the table.

  • Because your kickoff meetings will stop ending on downers when people realize that it will be weeks before developers can make pages live for them, or anticipation of developers challenging even the premise of the idea in the absence of data. It just feels 'too uphill.'

  • Because people tend to dumb their ideas down significantly when they know that they'll be relying on other people's time to deal with whatever comes of them. I'll be much bolder in initial copy, for instance, if I know I can walk it back quickly if a hunch doesn't play out.

And there are more and more things that come into play, but none of this is new. We've tried developing CMS systems that are more 'friendly' to 'non tech folks' and other things, but in reality, we just end up abstracting all the wrong things and end up giving them something that feels heavy, ill-suited and constraining.

What if the only bar to being able to put raw ideas on the Internet and see how people react to them was learning Github Flavored Extended Markdown and how to copy / paste / tweak a dozen or so React components where a more interactive experience is needed?

When we set up Docusaurus for any tech company, one of the VERY first things we do is provide them with components to embed conversations on social media, videos, arbitrary JS widgets (discord, twitch, etc) and guidance on how to handle images properly. This means their marketing teams don't need developer help in order to devise their experiments and rock on with them, nor do they need to learn some kind of software - they just need to know how to use a text editor and have a markdown cheat sheet.

While we Love Docusaurus and will be continuing to use and promote it, it's just one of many that you can use. Anything that lets you mix components with markdown naturally, with a styling system that's easily abstracted away means you're giving your marketing AND engineering teams equal footing to throw things at the wall. There's probably more friction here than you realize, unless of course you're a marketer.

Most of my best accomplishments in driving growth share a characteristic with my non-accomplishments: they started off as hunches and intuition I needed to see a bigger sampling of before I could explain them to someone else.

Knowing how uphill that can be, I learned to abandon ideas that required more than a trivial level of emotional investment quickly, or defending even just one could get so emotionally-draining that I'd need an entire day off to want to be around people again. That's a shame, because a bunch of great stuff never happened at Stack Overflow, mostly because I couldn't figure out how to back the idea with enough data to justify any engineering time being spent on it even just to see if it would incubate.

Don't let your company be like that. Free your marketing team so they can be contenders for adults in the room before you decide who the adults are going to be when growth slows and someone has to try something. Remove the clogs from the output side of things first.

MDX is a big step forward in that process and you need to make sure your marketing team has access to a platform that enables it.


A 45 Minute Introductory Call Is Free - Take Advantage Of It With No Obligation! →

The initial evaluation is free and there's no pesky sales follow up calls. If we don't get excited about working togther on the call, we won't pester you.

· 2 min read
Tim Post

We're excited to share that we're now casting for the following roles to begin filming immediately in the Baltimore / Metro area. The pay for all roles is $100 / hourly with wardrobe and style stipend, as well as catered meals on days that we shoot.

These roles are for customers that make technology products, such as software and hardware encryption keys. The productions will air on YouTube & other social / streaming sites.

If you're interested in any of these roles, please send a head shot and portfolio link to Matt Johnson (co-founder, in charge of casting) at matt@echoreply.io.

You must be 18 years of age, able to legally work in Maryland and be willing to sign a standard release. Some experience is strongly preferred (photo or video).

These roles require some hands-on experience writing or deploying code. You don't need to be a pro, but the bios need to resonate with you.


DevOps Pro

You're the person everyone wished directed support for their favorite products. You put up with Linux at work because it feeds your BSD time at home. There is nothing you cannot automate, including automating automation. But, somehow you still need to actually go out and work at a job. You dig it, but you dig you time doing whatever you want even more.

This role is being cast as identifying as female, between 25 - 60 years of age.

This role is needed for multiple shoots.

Lazy programmer

You copy and paste your old answers to brand new questions on Stack Overflow because really, when it comes down to it, that answer applies just as much today and voting to close questions is just too much work. 'Git' is just too damn long to type, as are most POSIX commands, so you have 26 one-letter symlinks your terraformer sets up for you.

This role is being cast as identifying as human between 18 - 60 years of age.

This role is needed for a single shoot.


Anyone interested should contact Matt at the address provided above.

· 3 min read
Tim Post

I don't think it's much of a stretch for those currently working in some capacity providing or in orbit around DevRel right now to see how I'm suggesting this connection. Our product, the thing they pay us for, is the production - we certainly guide the products as part of that, but at the end of the day, we're all actors.

Advocates utilize empathy in the opposition of their gols in order to understand how to make other voices heard. That, my friends, is getting in character, and then we somehow magically transform into another face entirely, training that keen sense of empathy outwardly, in order to help negotiate what you know to be the best possible compromise. That, dear friends, is also called getting into character, and it's a wonder we don't have more disgruntled theater majors in our ranks (I seriously only know of one, and don't keep tabs on their disgruntledness).

In order to be in a position to discover our career as actors, we probably started as community managers social workers, then went on to customer success or sales engineering, or marketing, and finally jumped into DevRel. And before any of that, we were software developers or something. But that's actually not really even subjectively true any longer, and that's what makes me excited. People are seeing that you don't need to really have 15 projects under your belt in order to understand programming enough to strongly empathize with pain and friction, and even be able to identify it.

This means that DevRel isn't just an essential role in a product-led industry, it's another conduit into the industry altogether. And I think companies that are struggling to hire for this role could very easily set their sights on people already set up to create amazing content and experiences who could very eaisly understand and creatively narrate your product.

I hope to strongly encourage this push and to be as welcoming to newcomers who feel like they might not have enough developer 'street cred' to be part of this amazing role that helps shape how tech gets built (and more importantly, influence what doesn't get built). Please know that for everyone who feels like their coding skills are lacking, there's 10 developers who would rather rewrite VB.NET than go anywhere near a camera.

And if you need a friend in the industry, I'm @tinkertim all over the place.


A 45 Minute Introductory Call Is Free - Take Advantage Of It With No Obligation! →

The initial evaluation is free and there's no pesky sales follow up calls. If we don't get excited about working togther on the call, we won't pester you.

· 5 min read
Tim Post

The sun has just about set on another Saturday evening and I've spent a lot of time thinking about personalities. Some thinking has been about my own and who I need to be for Echoreply to be successful, as well as who Echoreply needs to be as it starts taking off from the soul shard or two that I put in it.

We as marketers are charged with personifying organizations in an effort to make them more relateable, and if you follow frozen beef sheets on Twitter, you're looking at a new professional art form. We as marketers do this extremely well and that .. worries me sometimes in the world of software that we live in.

I've arrived at corporate personification being harmful and I need no other evidence beyond how much effort we believe is required for human beings to relate to other human beings on behalf of a brand. Why do we insist that organizations, comprised mostly of human beings, are less human and fallable than the sum of the humans they consist of? Why don't we just be ourselves and humans the 99.5% of the time that just being ourselves would be perfectly sufficient? I've come to call this "The Cult Of Tech Company Personalities" after also observing that most PR disasters I've ever directly been involved with or caused could have been averted had I just let people be themselves. This cult-like behavior really can grab ahold of you.

This phenomenon constantly tasks me because we try our best to help our clients NOT be like this; why we "Vulcanize" all of a sudden when speaking on behalf of our brand is something that keeps me up late at night and in the shower until the water runs tepid.

My approach, thus far, has been to integrate myself as much as possible in our client's product workflow and essentially bring out the character traits that the organization already has, in the form of writing guidelines and media standards that are needed for everyone to happily human together consistently when pointed outwardly.

There's always a point where people begin to wonder if the voice is too genuine; despite strict observance of all expected formailities, norms and other things, and zero evidence that changing anything would be a good idea. But, despite admitting it's irrational, our own comfort often makes us sound less like people when we communicate while working in general, magnified by 10 if we're outward-facing.

As humans we know "too nice" when we see it, often because our reaction to it is sufficiently viscereal that we can't really anticipate it. Echoreply is one of the few companies nuts enough to put serious engineering muscle into brand voice KPIs, so it leaves us with a bit of our own personality helix to decode. And that, folks, is fun stuff to work on.

We currently do a pretty good job of tracking the impact of even miniscule changes to any part of our funnels, even completely unintentional ones that we weren't specifically monitoring for -- this is thanks to really great observability and testing platforms that integrate effortlessly. However, social sentiment as well as plotting likely emotional influences in and between data sets is almost always left up to anecdotal observations distilled down by senior leaders - in other words, it goes 'out back' to die.

We need to help bridge the "I can see this anecdotally" -> "I can Show You Where This Has Been Hiding" gap. Put another way, you notice when those you trust have even tiny changes to their personalities, which can sometimes make friendships with people who are still finding their authentic selves rather diffifcult at times. Unfortunately, we far too often overcorrect for this presumption when we think about it in the sense of our business and all too often deliver ourselves like pretentious, bland and strikingly overpriced theme park food.

Echoreply's process (currently in development) flips this on its head, asserts that humans are perfectly capable of relating to one another with their own personliaties, and implements only a minimal amount of structure on communications. That's usually a very bad idea, unless you can monitor it in real time and chart corrections organization-wide in how you relate to people.

That's what gets me out of bed every day. I'm sick and tired of all the product super hero stories revolving around someone in CS or DevRel or somewhere else having to break ranks and just be human instead. Why don't we just, y'know, do that by default? I can't wait to bring that to reality with all the guard rails it needs to work.

And thanks for helping me think out loud as the sun warms the front face of our house. This and more highly-specialized KPIs will soon be available to design partners in their client area, and also available via version-0 of our REST API which is coming out a month from tomorrow.


A 45 Minute Introductory Call Is Free - Take Advantage Of It With No Obligation! →

The initial evaluation is free and there's no pesky sales follow up calls. If we don't get excited about working togther on the call, we won't pester you.

· 4 min read
Tim Post

What's the big deal about Monthly Active Users? Some of you might know the answer to this right away, but this metric has quite a bit of nuance to it and often partly eludes new founders especially when they're building a business around an already vibrant and active community.

It's a metric that you hear venture capitalists talking about quite often, and in plain English it's almost as simple as "grilled cheese sandwich", right? The name of the metric is literally the thing that goes into it, where's the ambiguity?

It's that whole active thing, as well as why you want to know that matters. I'm writing this primer because I want to save time on the free 45 minute discovery call that we provide to those interested in being design partners to hear about them instead of them hearing me talk so much.

What's 'Active', Precisely?

Please don't hate me when I say that the definition depends on why you want to know, and that's important because it can be very expensive if you get it wrong. The main reasons for wanting to know are charting growth, reporting to a vendor for billing, or reporting specific kinds of growth to investors.

Let's go over how you'd chart it if I were one of those things:

If I'm A Growth Manager

I'm not really all that interested in the background noise of people who simply hit the product while logged in and do nothing else, in most circumstances. That of course depends on the product, but I generally don't count users as active until I see them coming to the product with a very specific intent.

Someone that hits the site three times and then updates their profile would be active, though, just as someone that logged in from a specific CTA (say, from a landing page or ad) would be counted even if they didn't follow through with whatever the thing was.

I want to see that there are living organisms in my ecosystem that respond to things, and that those organisms multiply.

If I'm A Vendor

I care about every time a human being makes my service do work in order to estalblish that one of your organisms is in fact a human and authorized to see the page they're requesting, if I handle auth for you. Or maybe I care about the number of people that will need SMS codes sent to them if I'm your SMS gateway.

So, my active user count is going to look a bit different from your active user count, because my definition of active is just knowing who a user is and what they're allowed to access.

If I'm An Investor

I want to know that you have a growning developer user base, and that you're able to flip switches that causes them to engage in certain ways. While you may have 100,000 MAUs by your API gateway's definition of active, I only care about the 11% subset that are in a beta group, and only 6% of Those in that group doing a specific thing.

But It's Not A Relative Metric?!

It, well, generally isn't for reporting purposes. You'll find a way to define it that excludes noise effecitvely without too much squelch, but that's only going to matter to you internally. You may say "Wow, I have 100,000 MAUs!!!! ZOMG WOWS WOWS" and you should feel great about that!

Just keep in mind that your vendors think you've got twice that many, and investors might look at you like you just dropped a crazy valuation on Shark Tank when you tell them how you're actually defining it.

In modern times, a data lake with tools to query it are your best bet, along with plenty of help from scientists to separate signal from noise. Something that excites me daily are new platforms that make spotting gems in the data mine much easier, and we'll be talking more about them soon in a new series about growth hacking coming up next month!


A 45 Minute Introductory Call Is Free - Take Advantage Of It With No Obligation! →

The initial evaluation is free and there's no pesky sales follow up calls. If we don't get excited about working togther on the call, we won't pester you.

· 4 min read
Tim Post

I'm often asked, "Should the person handling Developer Relations report to Product or Engineering?"

Sometimes, the answer is "yes", but most often, the answer is "neither" and what comes next might just surprise you - we've seen the best success when DevRel reported into Marketing. The reasons for this are also interesting:

  1. It prevents power dynamics from short-circuiting the advocacy function that the Developer Relations role critically supports. You can't be annoying, even professionally annoying, if you're worried about how it's going to affect your comp or performance review. That may NEVER be a problem where you are and if it's not, then fantastic. But you need to think about it hard.

  2. It tightly couples messaging that's given across a variety of contexts to fill a variety of needs. The reason you have a DevRel is to communicate outwardly beyond what the marketing for top-down adoption strategies is communicating. If you're reporting into the marketing wing, you're constantly perfecting this with them, and it's subsequently stronger.

  3. It lets you set DevRel as a goal for anyone junior on your marketing squad. Don't just wait for engineers to realize they take a shine to the marketing stuff, let marketers also feel like they can take a shine to the engineering stuff. What matters is real voices come out.

DevRel really is about the show which is why we really feel like it belongs in the creator space as much as it does anywhere. We're storytellers with a knack for simplifying complicated concepts; having been an engineer is one way of acquiring that, but certainly not the only one.

What About Reporting To Sales Engineering Or Support Engineering?

Those would also be fantastic choices for DevRel to report to. In fact, it might actually be preferable if there is an unusually high "touch" count for onboarding to your product, because it's certain to ensure the DevRel stays very focused on friction points as they work with the product folks, and saves lots of time back and forth.

Similarly, if you're at a point where your value proposition still requires a complicated demonstration, it might make sense for the DevRel to report into the sales wing as sort of a bastion against breakage for client workflows.

Whatever makes sense, but again, keep in mind that advocates need to, well, advocate - make sure there's no conflict of interest with self-advancement from just doing their jobs.

This Doesn't Change The Universal Hat Stand Function Of DevRel.

Often called the glue that binds multiple teams together, we also have to ensure that if just one role is super-optimized with whatever is needed to operate with great autonomy between teams, it's this one. So before you go changing who reports where, it takes a special kind of manager to help developer advocates succeeed.

One day you're learning about pain points in a language you've never used before; the next day you're recording a feature demo, and then you need to put some time into thinking about how you can get your users the best deal in a controversial feature update - my point is, you don't produce consistent artifacts just by working consistent hours every week. Managers need a great deal of trust and emotional grown-upness to grow people in this role.

You Can Also Just Hire Us And Think About More Important Things Right Now.

We can take care of most early needs until you're getting close to realizing launch and making some hires, and it's extremely affordable.


A 45 Minute Introductory Call Is Free - Take Advantage Of It With No Obligation! →

The initial evaluation is free and there's no pesky sales follow up calls. If we don't get excited about working togther on the call, we won't pester you.

· 2 min read
Tim Post

Developer Relations and Developer Marketing On Demand is a service by Echoreply that lets you access professional narration of and evangelism for products made for software developers without hiring a full time person to do this.

Our service is unique in that we strictly deal with developer marketing and we have strong engineering backgrounds; we're the hybrids that can both spot and appreciate the wow points in developer tooling. The reason that typical marketing companies don't make material as authentic as what you can do in house is it takes many kinds of specialization to see the entire picture.

Now, it's more affordable and accessible than ever. During our design partnersnip phase, we're distilling a vast mix of Marketing / Public / Developer Relations core competencies into services that can be augmented or based on software that we create which provides immediate value to early-stage companies, starting at the consultation.

Look for more soon, in the meantime, welcome to our MVP launch and thank you for your interest!


A 45 Minute Introductory Call Is Free - Take Advantage Of It With No Obligation! →

The initial evaluation is free and there's no pesky sales follow up calls. If we don't get excited about working togther on the call, we won't pester you.