Contributor Signup


Thanks a lot for your interest in becoming a TechSnips contributor! You are well on your way to monetizing your hard-earned tech knowledge! To give you a complete picture of what you're in for, we've created an FAQ up front to ensure full transparency from the start. Please review this welcome section and if you're still interested, please fill out the small form at the bottom with your audition snip, and we'll get back to you.

What's in it for me?

Let's start off with what you came here for. How much better off will you be if you decide to contribute to TechSnips? There are significant benefits to regular contributors.

Promote yourself and your personal brand for marketing

Every snip will have a professional, custom intro animation added to it with the snip title, your name and your Twitter handle. Great for exposure! An example of this intro animation can be found here.

Adam will also be promoting those contributors that show dedication to TechSnips by submitting snips but also showing improvement in snip quality.

Improve your presentation skills

Since every snip published will go through an editing process and you may work with an editor (if any major problems), you'll be able to spot your weaknesses in delivery and recording quality helping you become a better presenter. Once your snip is published you'll then be able to see what a polished version of it looks like.

Record once, get paid monthly forever

As a contributor to TechSnips, you will also be paid for your knowledge over time with our royalty model. If you can come up with solutions for problems other technology professionals are having, can explain your answer in a clear, concise manner and can record it, you will be paid. How much you ask? That depends.

Payments will be disbursed monthly as royalties and can get a little confusing so let's use an example.

Let's say that at the end of a month:

  • TechSnips has generated $10,000 in revenue
  • Revenue % allocated to all contributors is 40% (fictional, confidential number)
  • Total snip minutes viewed that month were 1,000 minutes
  • The total minutes viewed across all your snips is 100 minutes

This means that the minutes your snips were viewed ended up being 10% (100 / 1,000) of all minutes viewed that month. If the total revenue % set aside for all contributors was $4,000 ($10,000 * .4), that means your snips accounted for 10% of the value that was brought in so you should be compensated $400 ($4,000 * .10) for the month.

This royalty model ensures that we are in this together. The more popular your snips are, the more money you will make and the more money the business owner will make.

Do I have to be good at recording demos?

Nope. That's what editors are for! You don't have to be a professional presenter whatsoever. We appreciate the knowledge you have in your head, and as long as you can coherently convert that knowledge by screencast, we want you!

You will go through an initial approval phase where we will review a demonstration of the kind of content we expect. Once we agree on a specific standard, you just adhere to that standard and produce away!

At some point, we may consider providing training material around recording, but for now, you're on your own to figure out how your best screen and audio recording setup.

Any tips on recording?

Yes. Check out the Snip Recording Guidelines page.

What languages can I speak in?

At this time only English is allowed. If you're not a native English speaker, that's OK. However, we must be able to speak English clearly for our subscribers to easily follow along with your instructions without struggling to understand your accent.

Do I still own the content once I submit it?

No. Once you submit a screencast to TechSnips, it becomes the sole property of TechSnips. You may not freely share or sell the screencast elsewhere. You can, of course, record a screencast again using the same content. It just cannot be the same screencast you submitted to us.

What kind of content should I produce?

This is entirely up to you, but we would recommend going with topics that you are intimately familiar with. The more you know about a subject, the more authoritative you'll sound in your snips. Viewers appreciate that, and we expect you to either know a lot about the subject you're presenting on or have done the proper research to hit all angles of the topic.

Because snips are so small and targeted, everyone in tech has thousands of potential snips they are capable of. What do you enjoy to do? What are you good at? Build snips based off of those things.

However, keep in mind that just because you're great at something doesn't mean we're looking for that kind of content. Don't record a snip before you are approved to do so else you may be wasting your time. 

What is a snip?

A snip is a 1-10 minute long demonstration screencast delivered by an expert in the field (you!). Each snip is highly targeted to a particular scenario that a technology professional may be looking for.

A snip is not simply rote documentation delivered via screencast. Every snip will undoubtedly contain the same information as plain documentation, but it's given via an expert in the field that will provide his or her unique insight and experience to that topic.

Each snip is scoped small to deliver exactly what the subscriber is looking for. Snips are not online courses with information that a system administrator must go digging through to find what she's looking for. Some good examples of snips may be:

  • How to Convert a Hyper-V VM to VMware
  • How to Query Windows Services with PowerShell
  • How to Create an Azure App Service
  • How to Install Visual Studio

Each snip is scenario-based; not necessarily about a particular product or service. For example, a snip could contain demonstrations surrounding multiple products if those products are frequently used in the same sitting.

An excellent way to think about a snip is to envision a script that someone in IT may write to perform a particular task. The contents of that script would most likely equate to a snip. It is a solution to a problem a subscriber is trying to solve regardless of all of the technologies it touches.

We don't need your slides, fancy outlines or long-winded introductions either. TechSnips' sole purpose is to provide laser-focused, scenario-driven screencasts that get down to brass tacks immediately.

All snips will be different but here's a good example of one. It gets to the point, it's simple and straightforward.

How is the snip flow supposed to go?

Every snip is going to be a little different and everyone has a unique style. We're not here to stifle your personal touch, however, we do require that you adhere to a few rules:

  1. Get right to it. No introduction. The most you should mention up front as an intro is perhaps a single sentence.
  2. Always mention any prerequisites up front. Does your snip require a specific operating system? A certain version of an application? Let people know what you're working with.
  3. Never ever, ever use slides! Technical, how-to content is always best presented with screencast demos.
  4. Do not go outside the scope of your snip. Remember - laser-focus. You can always do another snip. Demonstrate only what you would want to know if you needed to watch this snip. However, include everything necessary to solve the problem at hand. This is where upfront topic planning and the approval process will come in handy.
  5. Don't hesitate for long periods or show that you obviously haven't practiced this before or have no experience whatsoever with the topic. This will require heavier editing or result in denying your snip. Practice on your own a couple times before recording to ensure you can deliver the snip confidently.
  6. Keep it to no more than 15 minutes. Most snips will most likely be 7-10 minutes. If a snip is longer, it can be logically broken up into a playlist later.
  7. Do not add a summary at the end. One sentence is fine telling viewers you are complete.

Do I have to contribute a certain amount?

No. You are free to contribute as much or as little as you wish once approved. 

Where do I go if I have other questions?

For all questions related to being a contributor, you may email us at

I'm sold. Where do I sign?

If you're interested in joining us, please fill out the audition form at the bottom. We need to know your name and email address to contact you and we need an audition snip. This will be a typical snip. If approved, this can even be your first snip on TechSnips!