Code with AI Series: Build Real Software with Vibe Coding (CRM) - Event 3

This isn’t just another coding sprint. It’s an opportunity to:

• See specs come alive: watch how the AI-generated specs and domain model from Event 2 evolve into real CRM workflows: Contact creation, Deal pipeline, Activity logging, and Permissions.
• Shape user experience with Vibe Coding: apply vibe patterns to not just code, but also to design and UX flows.
• Expand Cursor-driven development: use Cursor to enforce code-quality, guide refactoring, and ensure the generated code follows the evolving spec contracts.
• Deliver working features: by the end of Event 3, we aim to have:
• A running backend service with functional APIs.
• A basic frontend UI wired to the APIs (add/edit contacts, deals, activities).
• Contract tests running in CI against our living spec.
• An early demoable CRM prototype accessible by participants.

Why should you Attend?

• You want to see AI-driven specs turn into a working product.
• You’re excited about designing and testing real CRM workflows instead of abstract exercises.
• You want to learn how AI and Cursor work together to accelerate development while maintaining clarity and alignment.
• You’re ready to contribute ideas, feedback, or code that directly shape the evolving CRM.
• You’d love to be able to say: “I helped build a CRM from scratch in front of a live audience.”

Who can Attend?
Designers, developers, product thinkers, AI enthusiasts, and startup dreamers of all levels.
Whether you’re contributing to backend, frontend, UX, or just curious to see AI, specs, and vibe coding in action - this is where the vision from Event 2 transforms into a usable product.

***

Event 3 is a continuation of Event 2:
Once we’ve completed Event 2, here’s what we’ll have achieved and where we’ll go next:

• Domain Model Defined: Contacts, Accounts, Deals, Activities, Permissions.
• AI-Generated Specs: CRUD operations, search, auth, and webhooks.
• Pattern Library Created: Vibe prompts and rituals for consistency.
• Working Scaffolds: Backend services, a minimal frontend, and CI hooks.

Next Steps (for Event 3):

1. Wire Specs to Code: Use Cursor and AI workflows to translate the specs into fully functional API endpoints.
2. Implement Core Workflows: Contact creation, Deal pipeline stages, Activity logging, and Permission handling.
3. Design Basic UI: Create initial CRM screens (list views, forms, dashboards) that connect to the backend.
4. Setup Continuous Testing: Ensure all API contracts are validated automatically against specs.