Work Policy

1. Engagement format

Every project is fixed scope, fixed price, fixed timeline, typically 21 working days from kickoff to launch. We don't bill by the hour and we don't run open-ended retainers without a written scope underneath them.

2. Communication channels

• A dedicated Slack channel (or shared workspace) for day-to-day comms.
• Async-first: most updates live in Slack or Linear with screen recordings.
• One scheduled live check-in per week (30 min, your timezone) plus on-demand calls when something needs talking through.
• Senior owner reachable directly by email and Slack, no PMs in the middle.

3. Response times

• Slack messages during your working hours: under 2 hours.
• Email: under 4 working hours.
• Urgent production issues during an active engagement: under 1 hour, any timezone.

4. Scope and change management

The signed scope document is our contract with future-us. Anything new gets handled as a written change request with its own price and timeline. We never silently expand scope or back-bill you.

5. Deliverables

• Code, deployed to your accounts (Vercel, AWS, GitHub) on day 1 of the engagement.
• Figma source files for every screen we design.
• A handover document covering architecture, environment variables, third-party services, and how to extend each feature.
• A recorded walkthrough video of the live product on launch day.
• 1–2 weeks of post-launch support included.

6. Code quality and security

All code is reviewed by a senior before merge. Secrets are stored in your own secret manager, never in source control. Production deploys go through a staging environment first. Dependencies are pinned and audited at handover.

7. Confidentiality

Everything you share with us, code, designs, roadmaps, customer data, is confidential by default. We sign NDAs on request before the first scoping call. Internal access to your project is limited to the team actually working on it.

8. Out of scope

• Ongoing customer support of your end-users (you own that).
• Marketing, ad spend, and SEO content (we can recommend trusted partners).
• Content writing for your product beyond placeholder copy (we'll structure where copy goes; you write the words, unless we agree otherwise in scope).

9. Project pause

If you need to pause an active engagement, we'll do our best to accommodate but cannot guarantee the same team availability when you restart. Pauses longer than 30 days may trigger a re-scoping fee.