Engagement

How we work

Last updated: September 19, 2026

A project engagement with APP0110 Labs is structured around clarity, written agreements, and direct access to the people building your software. Here is what to expect from first contact through handoff.

Stage 1 · Week 1:
Discovery

After you submit our intake form, we schedule a 30–45 minute call to understand the problem, your context, and your constraints. We exchange a mutual NDA before this call if you prefer — just let us know in the form.

This call is not a sales pitch. We use it to figure out whether there is a real fit, what the right shape of an engagement looks like, and whether we are the right team for the work.

Stage 2 · Week 1–2:
Scoping & SOW

Based on the discovery call, we write a Statement of Work covering:

• Specific deliverables and acceptance criteria
• Pricing (fixed-bid for defined scope, weekly retainer for exploratory work)
• Timeline with concrete milestones
• IP ownership (you own everything we build for you)
• Confidentiality terms
• Change-order process for mid-engagement scope changes
• Payment schedule

You review, redline, and sign before any paid work begins. We almost never start work on a verbal agreement.

Stage 3:
Build

Cadence depends on engagement type:

• Sprint engagements (2–6 weeks): weekly demos, async written updates via your preferred workspace (Slack, Teams, Linear, GitHub).
• Build engagements (6 weeks to 6 months): bi-weekly demos, weekly written status, mid-engagement architecture review.
• Retainer engagements (ongoing): monthly retrospectives, transparent hours and throughput dashboards.

Throughout the engagement you have direct access to whoever is doing the work — no project manager intermediary, no account executive layer. The people who write your code are the people you talk to.

Stage 4:
Handoff & support

At project close you receive:

• All source code in your Git repository, with clean commit history
• Complete technical documentation: architecture diagrams, deployment runbooks, environment setup
• A 30-day post-deploy support window for bug fixes (included)
• Optional: ongoing maintenance retainer

Pricing model

Engagements typically fall into three shapes:

For projects outside these ranges (very small or very large), we quote on request. We will not take on a project we do not believe we can ship.

NDA & confidentiality

We sign mutual NDAs before discovery calls. Send specs, code, and context without worry. All client work is treated as confidential indefinitely, including after the engagement ends.

IP ownership

You own all code, designs, and deliverables we create for you under the SOW. We retain rights to our pre-existing tools, libraries, and methodologies (which we may use across clients).

What we need from you

• A primary point of contact who can answer questions within one business day
• Access to relevant systems (read-only is fine to start)
• Timely decisions on scope changes (we will flag them within 24 hours of discovery)
• Payment per the SOW schedule