From first call to launch

The discovery call is a free 30-minute conversation — no pitch, no agenda other than understanding your business. We want to hear where you're spending the most time on things that shouldn't need your attention, where deals or customers are falling through the cracks, and what your team's operational rhythm actually looks like day to day.

Most clients come in with a general sense that "AI could help" but haven't identified the specific leverage points. That's what this call is for. We ask questions. We listen. We take notes. By the end of 30 minutes, we typically have a clear picture of the two or three workflows that would benefit most from automation — and the ones that aren't actually automation problems.

Booking is handled through our Whop calendar. You pick a time, receive a confirmation, and we show up prepared. Book a time here →

After the discovery call, we put together a written proposal that covers exactly what we'll build, how long it will take, and what it will cost. No ambiguity. No "it depends" line items. The proposal includes a defined scope of work, a delivery timeline with milestones, and the full project fee broken into payment stages.

Pricing is project-based, not hourly. You know the total before we start. The payment schedule is milestone-tied: typically a deposit before work begins and one or more payments aligned to delivery checkpoints. All invoicing is handled through Whop — you receive a professional invoice with your details, our details, and a clear line item for what you're paying for.

We don't start work until the proposal is accepted and the deposit is settled. That protects your investment and ours.

Once the engagement is underway, you get weekly written progress updates — what was completed, what's in progress, and if anything has changed in scope or timeline. For projects with a UI or client-facing component, you'll get access to a staging URL where you can see the system taking shape in real time.

Milestone reviews happen at defined points in the project. These are structured check-ins where we demonstrate what's been built, gather feedback, and confirm the scope before proceeding. Change requests are handled transparently: if a requested change is within scope, we build it; if it extends the scope, we write a short addendum to the proposal before proceeding.

We build on modern, well-supported infrastructure (Next.js, Python, Supabase, OpenAI APIs, Vercel) and write code that a developer you hire later can maintain without starting over.

Launch means your system is live, connected to your real data and workflows, and your team knows how to use it. We conduct a structured handover — a walkthrough of how the system works, how to monitor it, what the escalation paths look like, and how to make basic configuration changes without needing us.

Source code and documentation are transferred to you on delivery. You own everything we build. There's no licensing, no subscription to our infrastructure, and no dependency on us to keep the lights on.

The post-launch support window is defined in the engagement contract — typically 30 days. During this window, we'll fix defects, adjust logic based on real-world usage, and fine-tune the system. After the support window, ongoing maintenance is available as a separate engagement.