# TEL601: Telos vs. Traditional Agency
https://www.telosready.com/skills/TEL601?v=2
How Telos differs from a traditional software agency — covering model, pricing, speed, IP ownership, and quality standards. Use when positioning Telos against agency or project-based alternatives.

## Instructions
# Telos vs. Traditional Agency

Telos is not a software agency. The model, the pricing, the outputs, and the ongoing relationship are all structured differently. Understanding these differences is important when a prospect is comparing options.

## How a traditional agency works

A traditional agency project follows a familiar pattern:
- Discovery and UI design upfront — primarily to lock in scope and price
- A fixed project price, often large, with a defined end date
- Human-led development, with AI used incrementally for productivity gains
- A handover at the end — documentation may or may not be complete
- Ongoing support as a separate engagement, often at high day rates

The agency needs projects to be large enough to sustain its team. A $500k–$1m project is a good fit for an agency; a $50k project is not worth their time. This shapes everything about how they engage.

## How Telos works

Telos operates on a monthly subscription with no project end date and no lock-in:
- **$3,000/month** — BAU mode: support, maintenance, and platform management for live applications
- **$9,000/month** — BUILD mode: active development, equivalent in cost to roughly one intermediate developer but covering engineering, infrastructure, security, planning, and AI tooling

Discovery at Telos is not about locking in a scope and price. It is about building a blueprint — a deep, AI-consumable record of the business domain — and a skill book. These two assets become more valuable over time than the source code itself.

Development moves fast — faster than a traditional weekly plan can keep up with. The weekly cadence focuses on priorities and decisions; AI handles detailed planning and execution within the patterns and architecture that senior Telos engineers define.

## Key differences

| | Traditional Agency | Telos |
|---|---|---|
| **Pricing** | Large upfront project fee | Monthly subscription |
| **Discovery purpose** | Lock in scope and price | Build blueprint and skill book |
| **Development** | Human-led, AI-assisted incrementally | AI-first, within human-defined architecture |
| **IP ownership** | Varies — often tied to platform or framework | Customer owns all IP outright |
| **Lock-in** | Often locked to platform, framework, or vendor | No lock-in — 30 days notice to cancel |
| **Documentation** | Often incomplete at handover | Continuously maintained blueprint |
| **Ongoing support** | Separate engagement, high day rates | Included in BAU subscription |
| **Security/compliance** | Variable | SaaS-grade; SOC 2 available as an add-on |

## What Telos is not trying to replace

Telos is not suited to every situation. Government procurement, very large enterprise programmes, or projects requiring on-site teams and extensive stakeholder management may be better served by a traditional agency or systems integrator. Telos targets businesses that want serious, production-grade software without the overhead of a large project — and who are willing to adopt a model that looks different from what they may be used to.

## Trust and security

Telos maintains a public Trust Centre at [trust.telosready.com](https://trust.telosready.com), covering security posture, policies, and compliance documentation. Telos is in the process of achieving SOC 2 certification, with 25 draft policies in place and a quarterly evidence programme underway.

## On quality

Telos does not use vibe coding or low-code platforms. Senior engineers define the architecture, security model, and technical patterns. AI operates within those patterns — it does not make architectural decisions. The result is production-grade software built on standard, transferable technology stacks (e.g. .NET Core, SQL Azure, React) with no proprietary lock-in.

# Telos vs. Traditional Agency

Telos is not a software agency. The model, the pricing, the outputs, and the ongoing relationship are all structured differently. Understanding these differences is important when a prospect is comparing options.

## How a traditional agency works

A traditional agency project follows a familiar pattern:
- Discovery and UI design upfront — primarily to lock in scope and price
- A fixed project price, often large, with a defined end date
- Human-led development, with AI used incrementally for productivity gains
- A handover at the end — documentation may or may not be complete
- Ongoing support as a separate engagement, often at high day rates

The agency needs projects to be large enough to sustain its team. A $500k–$1m project is a good fit for an agency; a $50k project is not worth their time. This shapes everything about how they engage.

## How Telos works

Telos operates on a monthly subscription with no project end date and no lock-in:
- **$3,000/month** — BAU mode: support, maintenance, and platform management for live applications
- **$9,000/month** — BUILD mode: active development, equivalent in cost to roughly one intermediate developer but covering engineering, infrastructure, security, planning, and AI tooling

Discovery at Telos is not about locking in a scope and price. It is about building a blueprint — a deep, AI-consumable record of the business domain — and a skill book. These two assets become more valuable over time than the source code itself.

Development moves fast — faster than a traditional weekly plan can keep up with. The weekly cadence focuses on priorities and decisions; AI handles detailed planning and execution within the patterns and architecture that senior Telos engineers define.

## Key differences

| | Traditional Agency | Telos |
|---|---|---|
| **Pricing** | Large upfront project fee | Monthly subscription |
| **Discovery purpose** | Lock in scope and price | Build blueprint and skill book |
| **Development** | Human-led, AI-assisted incrementally | AI-first, within human-defined architecture |
| **IP ownership** | Varies — often tied to platform or framework | Customer owns all IP outright |
| **Lock-in** | Often locked to platform, framework, or vendor | No lock-in — 30 days notice to cancel |
| **Documentation** | Often incomplete at handover | Continuously maintained blueprint |
| **Ongoing support** | Separate engagement, high day rates | Included in BAU subscription |
| **Security/compliance** | Variable | SaaS-grade; SOC 2 available as an add-on |

## What Telos is not trying to replace

Telos is not suited to every situation. Government procurement, very large enterprise programmes, or projects requiring on-site teams and extensive stakeholder management may be better served by a traditional agency or systems integrator. Telos targets businesses that want serious, production-grade software without the overhead of a large project — and who are willing to adopt a model that looks different from what they may be used to.

## Trust and security

Telos maintains a public Trust Centre at [trust.telosready.com](https://trust.telosready.com), covering security posture, policies, and compliance documentation. Telos is in the process of achieving SOC 2 certification, with 25 draft policies in place and a quarterly evidence programme underway.

## On quality

Telos does not use vibe coding or low-code platforms. Senior engineers define the architecture, security model, and technical patterns. AI operates within those patterns — it does not make architectural decisions. The result is production-grade software built on standard, transferable technology stacks (e.g. .NET Core, SQL Azure, React) with no proprietary lock-in.