Most founders spend their first week of operations setting up tools. Creating a Notion workspace, configuring Slack channels, signing up for a CRM, connecting integrations, inviting teammates to each platform separately. By the time everything is "ready," a week of execution time has evaporated.
It doesn't have to take that long. Whether you use a single platform or stitch together multiple tools, you can go from zero to a fully operational startup workspace in 30 minutes , if you follow a structured playbook instead of making it up as you go.
This guide walks you through the exact setup steps for each operational function, with time estimates for each phase.
Why This Matters
The first operational decisions you make tend to stick for months. If you set up a messy project structure on day one, you'll be fighting that mess for the next six months. If you skip the CRM because "we only have three customers," you'll spend a painful afternoon reconstructing conversation history when you finally set one up.
Thirty minutes of deliberate setup saves dozens of hours of rearchitecting later. This playbook gives you a structure that works from 2 founders to 15 teammates without needing a rebuild.
What You'll Need
Before starting the timer:
- Your team list , names, email addresses (or wallet addresses if crypto-native) and roles
- Your active projects , the 2-5 things your team is currently working on
- Your customer/lead list , even if it's 5 names in a spreadsheet
- A workspace tool , this playbook works with any platform, but is written for tools that cover multiple functions (we'll use Pulsar Spaces as the reference implementation since it covers all steps in one platform)
Step 1: Create Your Workspace and Invite the Team (5 Minutes)
Start by creating your workspace and getting everyone in.
Set up the workspace:
- Create your organization/workspace with your company name
- Choose your plan (free tier works for teams of 5 or fewer)
- Set your workspace URL or identifier
Invite teammates:
- Add each team member with the appropriate role:
- Admin , founders and operations leads who need full control
- Member , core team members who need project access
- Guest , contractors, advisors, or part-time contributors with limited access
- Keep roles minimal at first. You can always upgrade permissions later; downgrading is awkward.
Time check: You should be at 5 minutes. Everyone on the team should have an invitation waiting.
Step 2: Set Up Your Project Structure (8 Minutes)
Don't create 20 projects. Start with what's active right now and add more as they emerge.
Create 3-5 projects based on your current work:
Most early-stage startups have some version of these:
| Project | Purpose | Example Statuses |
|---|---|---|
| Product / Engineering | Building the core product | Todo, In Progress, In Review, Done |
| Growth / Marketing | Getting users and customers | Ideas, Planned, Active, Complete |
| Operations | Internal processes, hiring, admin | Todo, In Progress, Done |
| Customer Success | Supporting existing users | New, Investigating, Resolved |
For each project:
- Name it clearly. "Product Development" beats "Dev" or "Eng Stuff."
- Set status columns. Start with 3-4 statuses max (Todo, In Progress, Done is enough for most projects). You can add more later.
- Add your first tasks. Move your current to-do list into real tasks with assignees, priorities and due dates. Aim for 5-10 tasks per project to start.
- Set project owners. Every project needs one person accountable for its progress.
Example tasks to create right now:
For Product: "Implement user authentication," "Design onboarding flow," "Set up CI/CD pipeline"
For Growth: "Write launch announcement," "Set up analytics tracking," "Create landing page copy"
For Operations: "Finalize contractor agreements," "Set up payroll," "Create team handbook"
Time check: 13 minutes total. Your project structure should be live.
Step 3: Configure Your CRM Pipeline (5 Minutes)
Even if you have three customers, set this up now. Future-you will be grateful.
Create your pipeline stages:
| Stage | What It Means | When to Move |
|---|---|---|
| Lead | Someone who might buy/use your product | Initial identification |
| Contacted | You've reached out | After first email/call |
| Qualified | They have the need, budget and timeline | After discovery call |
| Proposal | You've sent pricing or a proposal | After sending the offer |
| Closed Won | They're a customer | After agreement signed |
| Closed Lost | They said no (for now) | After rejection |
Add your existing contacts:
- Import from a spreadsheet if you have one, or manually add your top 10-20 contacts
- For each contact, note: name, company, email, current stage and last interaction
- Set follow-up dates for anyone you need to contact this week
Pro tip: Don't over-customize the pipeline. The six stages above cover 90% of startup sales processes. Add custom stages only after you've used the basic pipeline for a month and know what's missing.
Time check: 18 minutes total. Your CRM is live with your existing contacts.
Step 4: Set Up Communication Channels (4 Minutes)
If your workspace has built-in messaging, set up channels. If not, configure your Slack/Discord equivalent.
Create these channels:
| Channel | Purpose | Who's In |
|---|---|---|
| #general | Team-wide announcements, social chat | Everyone |
| #product | Product discussions, engineering updates, design reviews | Product + engineering team |
| #growth | Marketing, sales, customer feedback | Growth + sales team |
| #ops | Operations, admin, hiring, finance | Founders + ops |
| #standup | Daily async standups (what I did, what I'm doing, blockers) | Everyone |
Rules to communicate to the team:
- Project-specific updates go in the relevant project channel, not #general
- Decisions should be posted as a clear message, not buried in a conversation thread
- Urgent items use direct messages, not channel posts
- #general is for non-work chat and company-wide announcements , not task assignments
Time check: 22 minutes total. Communication structure is ready.
Step 5: Organize Your Files and Documents (4 Minutes)
Create a basic file structure. Don't over-organize , you need four folders, not forty.
Create these top-level folders:
| Folder | Contents |
|---|---|
| Company | Legal docs, agreements, cap table, corporate records |
| Product | Specs, designs, wireframes, research |
| Marketing | Brand assets, content, campaigns, analytics reports |
| Operations | Processes, templates, vendor agreements |
Upload your essential files:
- Move any critical documents from Google Drive, Dropbox, or wherever they currently live
- For now, focus on documents that at least two team members need to access regularly
- Don't try to migrate everything in one session , move files as you need them over the next few weeks
Time check: 26 minutes total. Files have a home.
Step 6: Configure Your Calendar and Integrations (4 Minutes)
Set up your calendar:
- Create your recurring meetings:
- Weekly team sync (30 min, all hands)
- Weekly 1:1s (30 min each, manager + direct report)
- Sprint planning / project review (if applicable)
- Enable project deadline inheritance (if your tool supports it) so project due dates appear on the calendar automatically
Connect essential integrations:
- GitHub , link your repositories for issue sync and webhook tracking (if engineering)
- Google Calendar , sync if your workspace calendar needs external calendar data
- Zapier/Airtable , only if you have existing automations to connect (don't set up Zapier "just in case")
Don't set up integrations you don't actively need today. Every integration is a maintenance cost. Add them when a real workflow demands it, not preemptively.
Time check: 30 minutes. You're done.
How Pulsar Spaces Makes This Easier
Pulsar Spaces covers all six steps in a single platform, which means you're not configuring six separate tools , you're configuring one workspace that includes projects, tasks, CRM, messaging, calendar, notes and files.
Specific advantages for this playbook:
- Workspace templates provide pre-built project structures so you're not starting from a blank canvas. Instead of defining status columns, channel structure and file organization from scratch, templates give you a starting point based on common startup workflows.
- Built-in messaging means Step 4 is just creating channels in the same tool where your projects live. No separate Slack signup, no integration configuration, no split context.
- Native CRM means Step 3 happens inside your workspace. Customer conversations, deal pipelines and project work are all visible in one environment.
- Calendar with project inheritance means Step 6 is partially automatic , project deadlines and task due dates flow into the calendar without manual entry.
- Claude AI assistant can help with setup: creating tasks from a list, organizing projects and generating summaries. It works across your projects, channels and CRM, so it has the context to be genuinely useful rather than generic.
The free tier supports 5 users and 2 workspaces , enough to follow this entire playbook without spending anything. The Startup plan ($49/month for up to 15 users) adds more workspaces, storage and integrations when you're ready.
Common Mistakes to Avoid
Over-structuring on day one. Don't create 15 projects, 20 channels and a 10-stage CRM pipeline. Start minimal and add complexity as real needs emerge. A project structure you actually use beats an elaborate one that nobody maintains.
Not assigning owners. Every project, every channel, every pipeline stage should have one person responsible. "Everyone owns it" means nobody maintains it. Assign owners on day one, even if the team is three people.
Skipping the CRM. "We'll set it up when we have more customers" is how you end up with six months of customer conversations scattered across email, Slack DMs and sticky notes. Three contacts in a pipeline is better than thirty contacts in your head.
Making channels for everything. You don't need a channel for every possible topic. Start with 4-5 channels and add more only when conversations are clearly happening that need their own space. Too many channels fragments attention the same way too many tools does.
Connecting every integration. Zapier, Airtable, webhooks , they're powerful when you need them, but every integration is a dependency that can break and requires maintenance. Connect integrations when a real workflow demands it, not because you might need it someday.
Your 30-Day Follow-Up Checklist
The 30-minute setup gets you started. This checklist keeps you on track:
Week 1
- [ ] Every team member has logged in and created at least one task
- [ ] Your top 10 contacts are in the CRM with current stages
- [ ] The team is using channels (not email or personal chat) for work discussions
- [ ] At least one recurring meeting is on the calendar
Week 2
- [ ] Every active project has at least 10 tasks with assignees and due dates
- [ ] The CRM pipeline reflects your actual sales conversations
- [ ] The team has settled into a communication rhythm (async standups, channel usage)
- [ ] One new hire or contractor has been successfully onboarded using this workspace
Week 3
- [ ] Review and clean up: archive completed tasks, update stale projects, remove unused channels
- [ ] Add any integrations that real workflows have demanded
- [ ] Write or refine your operating manual (where things live, how to use each tool)
Week 4
- [ ] Run a team retrospective: What's working? What's confusing? What needs to change?
- [ ] Adjust project structure, channels and CRM stages based on feedback
- [ ] Plan the next month's projects and populate the workspace accordingly
- [ ] Celebrate shipping work, not just setting up tools
Frequently Asked Questions
How long does it take to set up a startup workspace?
With a structured playbook, you can go from zero to a fully operational workspace in 30 minutes. This covers project structure (8 min), CRM pipeline (5 min), communication channels (4 min), file organization (4 min), calendar and integrations (4 min), plus team invites (5 min). The key is starting minimal and adding complexity as needs emerge rather than trying to design the perfect setup upfront.
What should a startup workspace include?
A complete startup workspace should cover five operational functions: work tracking (projects and tasks), communication (team messaging and channels), knowledge (documentation and files), relationships (CRM with pipeline management) and coordination (calendar with project deadlines). You can cover these with 5+ separate tools or with a single all-in-one platform.
How should I structure projects in a startup workspace?
Start with 3-5 projects matching your current work areas: Product/Engineering, Growth/Marketing, Operations and Customer Success. Each project should have 3-4 status columns (Todo, In Progress, Done is sufficient to start), a project owner and 5-10 initial tasks with assignees and due dates. Add more projects only when new workstreams emerge , don't pre-create projects for hypothetical future work.
What's the best free workspace tool for startups?
Pulsar Spaces offers one of the most generous free tiers for startups: 5 users, 2 workspaces, 5 GB storage and 2 active integrations with full feature access including projects, tasks, CRM, messaging, calendar, notes and files. Notion's free plan limits block storage and file uploads. ClickUp offers a free plan with limited features. Most CRM and messaging tools require paid plans for team use.
How do I get my team to actually use the workspace?
Three tactics: First, assign project owners so someone is accountable for each area. Second, reference the workspace in meetings , pull up the project board during standups, check the CRM during sales reviews. Third, redirect when people use the wrong tool , if someone assigns a task via Slack, move it to the workspace and reply "tracked it here." Consistent, gentle redirection builds habits faster than mandates.
Pulsar Spaces comes with workspace templates, built-in messaging, CRM and calendar , so your 30-minute setup happens in one tool, not six. Start free with up to 5 users.