Compare support options

Compare an employee, contractor or other support option against the same scope.

Consider the skills required, duration of the work, continuity, access to your team, and the founder time needed for decisions and feedback. Include the spending needed to run the work alongside the person's cost.

An illustrative developer-tool project might need a technical content specialist to reproduce an integration, explain it accurately and prepare distribution. A developer relations role might also include community participation and feedback to engineering; specify those responsibilities rather than assuming the title covers them. A specialist project might include a fixed research brief and a few decision meetings. An ongoing campaign role may need recurring review, operational access and responsibility for a wider program. Neither arrangement removes the need for clear decisions.

Use the support scenario planner with your own quotes and availability. It compares the inputs you provide; it does not estimate market compensation.

Today, write two viable options and one reason each could fail. Check whether you can supply the customer evidence, approvals and access required for either to succeed.

Read the contractor hiring guide if the work is a bounded external project.

Jon