When do you consider the project “done” and what are the acceptance criteria?

We consider your project “done” when every item outlined in your formal proposal has been fully designed, developed, tested, approved, and delivered to you. Your acceptance criteria are documented clearly from day one so you always know what to expect and how success is measured.

Your acceptance criteria are defined in your proposal
Before any work begins, we walk you through a detailed proposal that outlines:

• Every feature we will design and build
• The functionality and behaviors of your app
• All design deliverables required for your project
• Full user journeys, flows, and interface expectations
• QA requirements and technical specifications
• Infrastructure and deployment details
• The approval process for each milestone

These become the foundation for your acceptance criteria. Nothing is left open to interpretation.

Design acceptance criteria
Your design phase includes several major deliverables, each of which must be reviewed and approved individually before moving forward. A design item is considered complete only after it passes three approvals: senior development, project manager, and your own.

You will approve each of the following deliverables:

1. User Personas
   Approval confirms that your target audiences, motivations, behaviors, and goals are accurately reflected.
2. Site Mapping / Screen Mapping
   Approval confirms full alignment on app structure, navigation, and user pathways.
3. Wireframes
   Approval confirms the layout, functionality, screen structure, and UX logic before visuals are applied.
4. High Fidelity Designs
   Approval confirms final visuals, branding, spacing, typography, states, and responsive behavior.
5. Product Flows and Documentation
   Approval confirms detailed logic, functionality, use cases, and edge case handling for each feature.
6. Non Functional Prototype (NFP)
   Approval confirms your full clickable experience matches every detail of your design system and proposal.

Each deliverable must pass three required approvals:

• Senior development lead or CTO approval to ensure technical feasibility and scalability
• Project manager approval to ensure alignment with your proposal and user journeys
• Your approval to confirm everything meets your expectations

Only when all three approvals are complete is a design deliverable considered final and ready for development.

Frontend development acceptance criteria
You will approve each of the following deliverables:

1. Implemented User Interface
   Approval confirms that all screens match your approved high fidelity designs, including layout, spacing, typography, visual states, and responsive behavior.
2. Interactive Components and User Flows
   Approval confirms that all interactions, navigation, forms, transitions, and flows operate exactly as documented in your product requirements and NFP.
3. Animations and Microinteractions
   Approval confirms that loaders, transitions, feedback states, and motion behaviors match your design system and support the intended user experience.
4. Accessibility and Device Responsiveness
   Approval confirms that your app adjusts correctly across included devices, screen sizes, platforms, and orientations.

Each deliverable must pass the same three required approvals as design:

• Senior development lead or CTO approval to ensure technical accuracy and performance
• Project manager approval to confirm alignment with the proposal and design system
• Your approval during reviews to ensure everything meets your expectations

Backend development acceptance criteria
You will approve each of the following deliverables:

1. API Endpoints and Feature Logic
   Approval confirms that all endpoints function correctly, return the expected responses, and fully support your documented user flows.
2. Database Structures and Data Models
   Approval confirms that models, relationships, and schemas match your required logic and support long term scalability.
3. Authentication and Authorization
   Approval confirms that permissions, user roles, access rules, and security mechanisms function exactly as intended.
4. Background Jobs, Schedulers, and Services
   Approval confirms that automations, notifications, scheduled tasks, and background processes run reliably and follow your documented requirements.

Each deliverable must pass:

• Senior development lead or CTO approval for correctness, scalability, and reliability
• Project manager approval to ensure alignment with documented flows
• Your approval during feature reviews

Third party integrations acceptance criteria
You will approve each of the following integration deliverables:

1. Third Party API Connections
   Approval confirms that connected services such as Stripe, Twilio, SendGrid, Firebase, RevenueCat, Google Maps, or others function correctly and follow your documented flows.
2. Credential and Configuration Setup
   Approval confirms that all integrations operate under your accounts with correct API keys, permission levels, and security configurations.
3. Feature and Use Case Behavior
   Approval confirms that the integration performs exactly as expected, including payments, messaging, identity verification, analytics, or location services.
4. Error Handling and Edge Cases
   Approval confirms that each integration handles downtime, rate limits, invalid requests, and fallback scenarios according to your requirements.

Each deliverable must pass:

• Senior development lead or CTO approval for correct integration and system compatibility
• Project manager approval for alignment with your proposal
• Your approval once functionality has been demonstrated

Product architecture acceptance criteria
You will approve each of the following architectural deliverables:

1. Technical Architecture Plan
   Approval confirms alignment on frameworks, system structure, platforms, environments, databases, and security layers.
2. Scalability and Performance Planning
   Approval confirms that your system is structured to support growth, increased traffic, and future features.
3. Environment and Deployment Setup
   Approval confirms that development, staging, and production environments are configured under your accounts and meet your infrastructure requirements.
4. Architecture Documentation
   Approval confirms that technical decisions, system diagrams, flows, and configuration details are clearly documented for long term maintainability.

Each deliverable must pass:

• Senior development lead or CTO approval to confirm system stability and scalability
• Project manager approval to ensure alignment with your proposal
• Your approval to confirm clarity and alignment with your long term goals

Development acceptance criteria
Every developed feature must pass three checks before it is considered complete:

1. Internal QA approval
   Functional testing, regression testing, and device specific validation.
2. Project manager approval
   Verification that the feature behaves exactly as documented and designed.
3. Your approval
   You approve each feature during your weekly or bi weekly review meetings.

The project is considered complete when all deliverables are approved
Your project is officially “done” once:

• All design deliverables have been approved
• All frontend, backend, integration, and architecture tasks in your proposal are completed
• All QA tickets and edge cases are resolved
• Your UAT feedback has been fully addressed
• All repositories, servers, and accounts are fully set up under your ownership
• Production builds are prepared and ready
• The app is submitted to the App Store and Google Play Store (if included in your scope)
• All documentation, assets, and credentials are handed off

At that point, your product is ready for launch with full alignment on every requirement.

You can continue, pause, or take everything internal
After completion, you can:

• Continue with maintenance or new feature phases
• Move to a new fixed monthly proposal
• Switch to a retainer or hourly plan
• Pause and resume later
• Take everything internal at any time

Since all assets are built under your accounts, you always remain in full control.

Everything is documented and reviewed with you upfront
Your full acceptance criteria are spelled out in your proposal before work begins, and we are happy to review them in detail during a complimentary 45 minute consultation over Zoom. You can schedule that directly through our consultation page.

In short, your project is considered done when every design, development, integration, and architectural deliverable is completed, tested, documented, and approved exactly as outlined in your proposal. Our process ensures total clarity and confidence from start to finish.