Daymark
scope and price.

1. Agreed outcome

Give a founder one coherent workspace for turning an idea into an editable launch plan and tracking the next useful actions.

Intended first users: Early founders who need a structured first plan before investing in a multi-user production product.

2. Included scope

• Marketing, workspace, templates, research, signals, new-plan, and upgrade screens
• Reusable plan-detail and timeline screens
• Payment result, missing-plan, empty, loading, unavailable, and validation states
• Generate a structured plan from the founder's idea, audience, and constraint
• Edit the plan, questions, features, tasks, completion state, and effort estimates in browser storage
• View the derived timeline and continue to one hosted sample-purchase flow

3. Integrations and technical assumptions

• One narrowly configured AI generation response using the client's API account
• Browser-local plan persistence
• One hosted payment provider: Stripe or Razorpay

4. Client responsibilities

• Approved product language, planning framework, example content, and policies
• Domain, hosting, AI, and selected payment-provider accounts
• Decisions about model behavior, data retention, and acceptable generated content
• One decision-maker who returns consolidated feedback during each review window

5. Third-party costs

These are paid directly by the client and are outside the build fee.

• Domain and hosting
• AI model usage
• Payment processing and provider fees
• Database, authentication, email, monitoring, or analytics added in a later production scope

6. Outside this scope

• User authentication, server-side plans, shared databases, backups, or cross-device sync
• Teams, permissions, collaboration, notifications, subscriptions, or production billing
• A production administration area, analytics pipeline, or customer-support tooling
• Native mobile applications, complex agents, file search, or external knowledge bases

New pages, features, or integrations require a separate written quote and approval before they are added.

7. Acceptance criteria

• The agreed screens and reusable plan/timeline views load with working navigation
• AI creation returns the agreed plan shape and handles invalid or unavailable responses
• Plan edits, tasks, progress, and timelines remain consistent during the browser session and agreed persistence test
• The hosted checkout handoff uses the client's configured provider and agreed sample product
• The three agreed journeys pass on the agreed phone and desktop sizes

8. Payment, revisions, and support

A 50% start payment of $499.50 is due after scope acceptance. The remaining $499.50 is due after acceptance testing and before production launch.

Three consolidated revision rounds and thirty calendar days of fixes for defects in the accepted work.

9. Ownership and handoff

• Source repository and production accounts remain client-controlled
• The client receives the live URL, environment-variable list without secret values, launch checklist, operating guide, and architecture/data-flow documentation