Creating your first project in BuildOS starts with a natural conversation about what you want to build. Instead of filling out forms or choosing templates, you describe the work in plain language and BuildOS turns that input into a project with the right goals, tasks, documents, and plans. You can say things a form could never capture, like "I want to write a novel, probably literary fiction, maybe 60k words, exploring themes of memory and identity" — and BuildOS just works with that.
Open the chat, describe your project, and BuildOS figures out the rest.
How It Actually Works
Step 1: Choose "Start a Project"
Click the chat icon or press your keyboard shortcut. You'll see a screen that asks "How would you like to work today?" with options like General Chat, Project Chat, Start a Project, and Brain Dump. Choose Start a Project.
If you're brand new to BuildOS, the experience is even simpler — you'll see a welcome screen where "Create your first project" is the main action, with other modes unlocked after your first project is set up.
Step 2: Describe What You Want to Build
Just say it. Type naturally, like you're explaining your idea to a smart friend.
Examples that work well:
- "I'm building a mobile app for tracking fitness workouts"
- "I want to write a novel about time travel, probably 60k words"
- "I'm launching a newsletter about AI tools for small businesses"
- "I need to plan my wedding for October"
- "I'm starting a consulting business on the side"
- "I'm remodeling my kitchen, starting with layout and contractor bids"
You don't need perfect clarity. BuildOS will ask if it needs more.
Step 3: Answer Clarifying Questions (Maybe)
If your description is clear enough, BuildOS just creates the project. If not, it asks one or two focused questions — never more than two rounds. It only asks about what it truly needs: the type of project and what you're trying to create.
What BuildOS might ask:
- "What kind of project is this: a product you're building, something you're writing, or a business initiative?"
- "What's the main thing you're trying to create or accomplish?"
Answer naturally. If you realize mid-conversation that you described the wrong thing, just say so: "Actually, let me start over. This is really about X." BuildOS adjusts based on what you tell it.
Step 4: Your Project Takes Shape
BuildOS creates what makes sense for what you described — and deliberately starts simple. A straightforward project might just get a name and a goal. A more detailed description gets more structure.
Here's the building blocks BuildOS works with:
- Projects are the container. Everything else lives inside one.
- Goals are what you're trying to achieve. If you stated an outcome, you'll see a goal.
- Tasks are things you can check off. You'll get these if you mentioned specific actions.
- Documents hold notes and reference material. BuildOS may create a context document summarizing your project.
- Plans group related tasks into phases. These only appear if you described distinct workstreams or phases.
The idea is that structure grows naturally. You start lean, then add goals, tasks, and plans as your project evolves. Simple projects are good — you don't need a full plan on day one.
When the project is created, the chat automatically switches to your new project context. You'll see a confirmation message, and you can start working right away — ask questions, add tasks, or refine goals through the same conversation.
Two Real Examples
Simple: You tell BuildOS "I want to learn Spanish to conversational fluency by the end of the year."
BuildOS creates a project with one goal: "Conversational fluency." That's it. Clean starting point. From there, you can ask BuildOS to help you break it down further — research methods, set up a practice routine, find resources — and the project grows as you go.
Detailed: You tell BuildOS "I'm planning my wedding for October — we need to book a venue and catering, build out the guest list, and handle invitations on a separate track."
Because you described specific deliverables and separate tracks, BuildOS creates more structure: a goal for pulling off the wedding, tasks for the concrete actions you mentioned (venue, catering, guest list), and plans to organize the distinct workstreams. The structure matches what you actually said.
The difference isn't about project size — it's about how much you told BuildOS upfront. More detail in, more structure out.
After Your Project Exists
Once created, you keep working through the same chat. Here's what that looks like with the wedding project:
You: "I just found out the venue I want has availability in early October. I should lock that in before anything else."
BuildOS: "Got it. I'll add a task to confirm the venue booking and prioritize it at the top of your list."
You: "Actually, I want to split the guest list work into two phases: our side and partner's side."
BuildOS: "Done. I've created two plans to organize those separately."
You can also work directly in the project view — check off tasks, edit details, add notes. The chat and the direct interface work together.
Tips for Good Project Descriptions
Be specific about what you're making:
- "I'm building an iOS app for habit tracking" works better than "I want to make an app"
Include context when relevant:
- "I'm writing a 50k word romance novel, aiming to self-publish on Amazon" works better than "I want to write a book"
Mention phases if you have them:
- "I'm launching a marketing campaign — research phase first, then creative, then distribution by March 15" gives BuildOS enough to create real structure
But don't stress about perfection. If you're vague, BuildOS asks. That's the point.
Common Questions
"What if I don't know exactly what I'm building yet?"
Start anyway. Describe what you know: "I want to start some kind of side business, probably in the AI space, not sure exactly what yet." BuildOS creates a lightweight structure for exploration. You evolve it as you learn more.
"What if BuildOS misunderstands my project?"
Tell it. Say "This isn't quite right, it's more of a learning project than a business project" and BuildOS adjusts. You can also edit directly: delete tasks that don't apply, rename goals, add what's missing. The initial structure is a starting point, not a commitment.
"Can I change everything later?"
Yes. Nothing is locked in — add, remove, or reorganize anytime.
"How is this different from brain dumps?"
Brain dumps capture scattered thoughts that might span multiple projects or just need processing. Project creation is for when you know you want to start something specific. They're complementary — you might brain dump to discover a project idea, then create the project through the chat.
Your First Project: Just Try It
The best way to understand this is to do it. Open the chat, choose Start a Project, and describe something you actually want to work on.
Start with something concrete: that side project you've been meaning to organize, that trip you need to plan, that skill you want to learn. Describe it in a sentence or two. You'll have a project in under a minute.
Ready? Open BuildOS and describe your next project.