# How we work together, before you call us

Page: https://pixelteh.com/engagement · Last updated: 2026-11-19

_Engagement models_

Every engagement model, what each one includes, the terms that come with them and who we are a good fit for.

## Engagement models

Start with a free call. Your audit or discovery ends with a written estimate and, for new builds, a budget ceiling.

| Model | Best for | Starts / duration | Commitment |
| --- | --- | --- | --- |
| Code audit | Vibe-coded apps and smaller codebases you need to trust before you build on them | about 1 week | One-off |
| Takeover audit | Systems your business runs on, inherited from another team or a developer who left | 2 weeks | One-off |
| Discovery | New products, before anyone writes code | 2 weeks | One-off |
| Fixed-scope project | MVPs and well-defined builds | per scope | Per project |
| CTO as a service | Founders who need technical leadership without a full-time CTO hire | starts in 1 to 2 weeks | 3-month minimum, one month's notice |
| Team extension | Adding senior developers to a team you already run | starts in 1 to 2 weeks | 3-month minimum, one month's notice |
| Dedicated team | Products that need a whole team, with or without your own CTO | starts in 1 to 2 weeks | 3-month minimum, one month's notice |
| Time and materials | Evolving scope, support and smaller improvements | ongoing | None |

## What you get

### Code audit

- **Starts / duration**: about 1 week
- **Best for**: Vibe-coded apps and smaller codebases you need to trust before you build on them
- **Commitment**: One-off

Includes:

- Findings ranked by business risk, in plain language
- Security, data and deployment checks
- A written plan with what to fix first and what it costs

### Takeover audit

- **Starts / duration**: 2 weeks
- **Best for**: Systems your business runs on, inherited from another team or a developer who left
- **Commitment**: One-off

Includes:

- Code, hosting, security and data review
- Written report with risks ranked by business impact
- A plan to stabilise, then refactor or rebuild, with estimates

### Discovery

- **Starts / duration**: 2 weeks
- **Best for**: New products, before anyone writes code
- **Commitment**: One-off

Includes:

- Written scope with user roles, integrations and platforms
- Clickable prototype of the key flows
- A budget ceiling we don't exceed without your sign-off

### Fixed-scope project

- **Starts / duration**: per scope
- **Best for**: MVPs and well-defined builds
- **Commitment**: Per project

Includes:

- Fixed price for the agreed scope
- Milestones with a demo at each one
- Launch and the first weeks of fixes

### CTO as a service

- **Starts / duration**: starts in 1 to 2 weeks
- **Best for**: Founders who need technical leadership without a full-time CTO hire
- **Commitment**: 3-month minimum, one month's notice

Includes:

- Architecture, roadmap and code quality owned by a senior lead
- Plain-language updates on progress, risks and spend
- Engineers added as a dedicated team or team extension when you need them

### Team extension

- **Starts / duration**: starts in 1 to 2 weeks
- **Best for**: Adding senior developers to a team you already run
- **Commitment**: 3-month minimum, one month's notice

Includes:

- In-house engineers who work in your tools and rituals
- Trial period on request, free replacement if it isn't a fit
- Scale up in 1 to 2 weeks

### Dedicated team

- **Starts / duration**: starts in 1 to 2 weeks
- **Best for**: Products that need a whole team, with or without your own CTO
- **Commitment**: 3-month minimum, one month's notice

Includes:

- A named lead plus engineers working only on your product
- Demo cadence agreed at kickoff
- Scale up in 1 to 2 weeks

### Time and materials

- **Starts / duration**: ongoing
- **Best for**: Evolving scope, support and smaller improvements
- **Commitment**: None

Includes:

- Billed by the hours worked
- Clear reporting of where each hour went
- Same engineers who know your system

## Terms in plain words

- **Commitment**: Teams start with a three-month minimum.
- **Notice**: One month's notice to scale down or end a team engagement. Engagements can't be paused.
- **Scaling up**: New engineers join in one to two weeks.
- **Ownership**: All IP, code and repositories are yours from the first commit. Nothing is locked to us.
- **Confidentiality**: We sign your NDA, or send ours, before you share details.
- **Replacement**: If someone isn't the right fit, we replace them at no cost. A trial period can be arranged.
- **Budget ceiling**: Fixed-scope estimates come with a ceiling we don't exceed without your written sign-off.
- **Start**: Very small jobs can often start the next day, smaller engagements within a week, larger ones within two.

## Are we a good fit?

### Good fit

- You have a business running on the software, or a clear plan and budget for one.
- You want a long-term partner who says no when something is a bad idea.
- You care about owning your code and understanding the trade-offs.
- Your situation is one of ours, such as a takeover, a new product, a system to replace or a team to grow.

### Not a fit

- You want a copy of a famous app on a small budget.
- You need a one-hour fix with no plan to continue.
- You want the cheapest hourly rate above all else.
- You don't want to be involved in decisions.

## What we discuss on the call

**Discovery call**: Free · 30 to 60 minutes

Our COO and a senior engineer listen, ask the awkward questions and tell you what we would do first. You leave with a next step, whether or not it's us.

[Book a discovery call](https://pixelteh.com/contact#book)

## Frequently asked questions

### How do you price work?

Audits, discovery and well-defined projects are fixed price. Ongoing work runs as time and materials or a monthly team. You get a written estimate after an audit or discovery, before you commit to more.

### Do you work with fixed prices?

Yes, for audits, discovery and well-defined projects. Ongoing work runs as time and materials or a monthly team.

### What's the minimum commitment for a team?

Three months.
