Client Manual: How We Build Together

Welcome to Built by Dakic.

This document is our “rules of engagement.” It isn’t a legal contract; it is a user manual for our partnership. Its goal is to provide total transparency so you never have to wonder “what are they working on?” or “what do I need to do next?“

1. Our Philosophy

Balance & Speed. Our goal is to ensure a balance between your product’s success and our team’s sustainable happiness. We don’t believe in “black box” development; you will have full access and control over your code and resources at all times—no vendor lock-in.

2. The Process: Sprints & Meetings

We work in weekly sprints to deliver products in weeks, not months. Our workflow follows a simple cycle: Develop Idea → Prototype → Build → Launch → Support.

Meeting Cadence: Minimal & Focused

We strictly limit scheduled calls to maximize build time. There are only two scheduled meetings you need to plan for:

  1. The Planning Meeting: At the start of the engagement, this takes place on Monday.
  2. The Transition: As the project proceeds and a rhythm is established, we move the Planning Meeting to Friday, immediately following our Retrospective Meeting.

Task Management (The “Now, Next, Later” Framework)

To keep things clear, we organize all tasks into three specific buckets on our shared board:

  • NOW: Tasks for the current Sprint that align with immediate goals.
  • NEXT: Upcoming tasks to address in future Sprints.
  • LATER: Longer-term initiatives documented for future planning (Icebox).

3. Communication & Roles

Trust comes from predictability and clear lines of authority.

Required: Single Point of Contact

For every stream of work, we require one Single Point of Contact as well as a Designated Backup (in case the primary is unavailable).

  • The Authority: This designated person is the sole decision-maker on what is being done and in what order.
  • Why? This prevents conflicting feedback from multiple stakeholders and ensures the engineering team always has a clear, prioritized “Now” list.

What You Can Expect From Us

  • High-Velocity Delivery: We leverage AI to assist with coding, testing, and documentation to move faster without sacrificing quality.
  • Transparency: You will have visibility into the active sprint status.
  • Regular Updates: Expect regular updates so you always know where the project stands.

What We Need From You

  • Frequent Collaboration: We build with you, not just for you. We expect you to be present to guide the work.
  • Decisive Feedback: To keep the sprint moving, we need clear feedback on prototypes and builds quickly. Delays in feedback = delays in launch.
  • Assets Upfront: Please provide necessary assets (logos, copy, access credentials) before the sprint begins to avoid bottlenecks.

4. Tech Stack & Tools

We use modern, scalable technologies. While you don’t need to know how to code, it helps to know what’s under the hood:

  • Frontend: TypeScript, React, Svelte, Solid
  • Backend: Ruby on Rails, Elixir, Phoenix
  • Database: Neon, Supabase, Convex
  • Mobile: React Native, Flutter

5. Billing & Administration

  • Simple Pricing: Our rates start at $2.5K per week.
  • Payment Schedule: To maintain momentum, weeks are billed before every sprint.
  • No Surprises: Since we bill by the sprint, you continuously control the budget. We don’t rack up hidden hours; we focus on value delivered per week.