# The template should do the first setup step > Why scoped project templates, in-project document defaults, structured intake templates, sample-data previews, and private draft copies usually beat empty workspaces. - Canonical HTML: https://growth.iangoh.com/blog/the-template-should-do-the-first-setup-step/ - Published: 2026-05-29 - Updated: 2026-05-29T10:10:00Z - Categories: product-led growth, onboarding, SEO - Niches: SaaS, developer tools, creator tools, AI products, operations software ## On this page - Start from the job, not the blank canvas - Keep the instructions where the work happens - Use templates to protect internal structure without exporting internal complexity - Preview the future, then give the user a clean slate - Private drafts are a better trial surface than a sales carousel - A good template system is an onboarding surface, a product surface, and a search surface at the same time ## Start with these related tactics - [Team-scoped project template with milestones and owners](/growth-ideas/team-scoped-project-template-with-milestones-and-owners/): Let a team start from a ready-made project shape that already includes the milestones, issues, lead, and members the work usually needs. - [Document template inside the project where work starts](/growth-ideas/document-template-inside-the-project-where-work-starts/): Put the default spec or status-update template inside the live project instead of sending people to a separate docs ritual first. - [Template default properties for cleaner cross-channel intake](/growth-ideas/template-default-properties-for-cleaner-cross-channel-intake/): Use one intake template to prefill team, assignee, project, labels, and sub-issues so requests from Slack, email, or automation land with usable structure. A lot of products still greet a new user with an empty room and a pep talk. The room may be elegant. The copy may be polished. It still leaves the user doing the hardest part alone, which is translating a vague promise into the first piece of real work. Good template systems do not just decorate onboarding. They carry the first useful step. ## Start from the job, not the blank canvas [Team-scoped project template with milestones and owners](/growth-ideas/team-scoped-project-template-with-milestones-and-owners/) is a clean example. Linear does not ask a team to invent the shape of a repeated project every time. It lets the project come with the lead, members, milestones, and issues already in place. That belongs next to [bundled workspace template for the whole team job-to-be-done](/growth-ideas/bundled-workspace-template-for-whole-team-job-to-be-done/). One helps at the project layer. The other reminds you that sometimes the real activation unit is the whole workflow, not a single page. ## Keep the instructions where the work happens [Document template inside the project where work starts](/growth-ideas/document-template-inside-the-project-where-work-starts/) matters because the setup breaks when the user has to bounce into a separate ritual to find the brief. If the project already contains the spec shape, the next action is obvious. Fill in the missing facts. Start moving. I would pair that with [support-doc workflow tutorial for repeated questions](/growth-ideas/support-doc-workflow-tutorial-for-repeated-questions/). Both tactics accept the same reality: people learn faster when the explanation sits beside the action, not in a separate cave. ## Use templates to protect internal structure without exporting internal complexity [Template default properties for cleaner cross-channel intake](/growth-ideas/template-default-properties-for-cleaner-cross-channel-intake/) is useful because most outside users should not have to learn your routing map. They should be able to ask from Slack, email, or an automated flow and still create something your team can work with. The template carries the taxonomy quietly. This sits well beside [ask intake on the surface people already use](/growth-ideas/ask-intake-on-the-surface-people-already-use/). One reduces user friction. The other keeps your internal system clean enough to trust. ## Preview the future, then give the user a clean slate [Template preview with sample data and one-click reset](/growth-ideas/template-preview-with-sample-data-and-one-click-reset/) solves a common problem. Empty templates are hard to evaluate, but fake data can also make the product feel noisy. Airtable's pattern is useful because the preview teaches the shape first, then lets the user wipe the examples when they are ready to work for real. That naturally connects to [guided template preview before setup](/growth-ideas/guided-template-preview-before-setup/). Show enough of the destination that the user can understand the promise. Do not trap them in demo clutter afterwards. ## Private drafts are a better trial surface than a sales carousel [Community template copy lands in your personal drafts](/growth-ideas/community-template-copy-lands-in-your-personal-drafts/) is the move I wish more template marketplaces copied. The moment a user can duplicate something into a private draft, the gallery stops being a brochure. It becomes a low-risk place to test taste, fit, and purchase intent. It also pairs nicely with [Figma Community first-page preview for paid files](/growth-ideas/figma-community-first-page-preview-for-paid-files/). One gets the user over the first inspection step. The other gives them a safe place to play after curiosity turns into intent. ## A good template system is an onboarding surface, a product surface, and a search surface at the same time This cluster fits SaaS, developer tools, creator software, AI products, and operations products especially well. If I were auditing a setup flow this week, I would ask five plain questions. Does the template start from a real job. Are the instructions inside the work. Does the intake preserve structure without forcing the user to learn it. Can the user see realistic sample data before committing. Is there a safe private place to try the asset before they buy or share it. If you want help turning templates, onboarding, and crawlable product proof into one acquisition system, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [Team-scoped project template with milestones and owners](/growth-ideas/team-scoped-project-template-with-milestones-and-owners/) - Product, Onboarding, Website - [Document template inside the project where work starts](/growth-ideas/document-template-inside-the-project-where-work-starts/) - Product, Content, Operations - [Template default properties for cleaner cross-channel intake](/growth-ideas/template-default-properties-for-cleaner-cross-channel-intake/) - Support, Product, Operations - [Template preview with sample data and one-click reset](/growth-ideas/template-preview-with-sample-data-and-one-click-reset/) - Website, Onboarding, Product - [Community template copy lands in your personal drafts](/growth-ideas/community-template-copy-lands-in-your-personal-drafts/) - Community, Product, Onboarding - [Guided template preview before setup](/growth-ideas/guided-template-preview-before-setup/) - Product, Templates, Activation - [Bundled workspace template for the whole team job-to-be-done](/growth-ideas/bundled-workspace-template-for-whole-team-job-to-be-done/) - Marketplace, Product, Website ## Essay chronology - [Newer essay: The listing should do the first minute of onboarding](/blog/the-listing-should-do-the-first-minute-of-onboarding/) - marketplaces, product-led growth, trust surfaces - [Older essay: The site should have a page for the question the buyer typed](/blog/the-site-should-have-a-page-for-the-question-the-buyer-typed/) - seo, buyer intent, content architecture ## Keep reading - [The next step should already be there](/blog/the-next-step-should-already-be-there/) - product-led growth, onboarding, SEO - [The Airtable base should survive the template copy](/blog/the-airtable-base-should-survive-the-template-copy/) - template-led growth, onboarding, SEO - [The help page starts earning when it can finish the job](/blog/the-help-page-starts-earning-when-it-can-finish-the-job/) - support-led growth, seo, activation ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path - [developer tools](/blog/#path-developer-tools) - 3 essays in this path ## Sources - [Linear Docs: Project templates](https://linear.app/docs/project-templates) · [GrowthDex source hub](/sources/linear-docs-project-templates-linear-app/) - [Linear Docs: Project documents](https://linear.app/docs/project-documents) · [GrowthDex source hub](/sources/linear-docs-project-documents-linear-app/) - [Linear Docs: Issue templates](https://linear.app/docs/issue-templates) · [GrowthDex source hub](/sources/linear-docs-issue-templates-linear-app/) - [Airtable Support: Using Airtable templates](https://support.airtable.com/docs/using-airtable-templates) · [GrowthDex source hub](/sources/airtable-support-using-airtable-templates-support-airtable-com/) - [Figma Help Center: Duplicate Community files](https://help.figma.com/hc/en-us/articles/360038510873-Duplicate-Community-files) · [GrowthDex source hub](/sources/figma-help-center-duplicate-community-files-help-figma-com/) ## Editing notes - Kept the essay on one claim: the template should carry the first useful setup step instead of leaving the user in an empty room. - Used plain objects like milestones, issue defaults, sample data, drafts, and specs instead of generic onboarding language. - Cut product-marketing puffery and let the setup mechanics make the argument. - Ended with a short operator checklist and direct advisory CTA instead of a generic conclusion. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.