# Projects: Defined work delivered for an agreed fixed price.

URL: https://extra.dev/engagement/projects
Typical length: 1 month and up
Delivery: Led and managed by us
Pricing: Fixed price
Payments: By agreed milestones

**Defined projects delivered for a fixed price**

A defined project delivered for a fixed price. We agree the scope, delivery plan and acceptance criteria before work begins, then review progress with you throughout.

We define the work before committing to a fixed price. The agreed scope sets out the expected outcome, requirements, assumptions and acceptance criteria. It also makes clear what we will deliver and what decisions or input we need from you.
We manage the work against that agreement and review progress with you as it develops. When a requirement changes, we assess its effect on the scope, price and delivery plan, then agree how to proceed.

Includes:
- **Project Management**: Planning, coordination, and delivery management.
- **Design**: Product design, UX, UI, and design systems.
- **Web**: Front-end, back-end, and full-stack web development.
- **Mobile**: Native iOS and Android, and cross-platform apps.
- **Desktop**: Native and cross-platform apps for macOS, Windows, and Linux.
- **AI / ML**: Generative AI and agents, computer vision, and predictive models.
- **Embedded & IoT**: Firmware, on-device control, and fleet management.
- **DevOps**: CI/CD, cloud infrastructure, observability, and security.
- **QA**: Automated and manual testing, load, and security.

A good fit when:
- The scope and acceptance criteria can be agreed before delivery begins
- You want us to take responsibility for delivering the agreed work
- You need a fixed price and delivery plan before committing

Not the right shape when:
- You need to assess the problem or define the work before committing to delivery: start with Workshops
- Priorities and scope will continue to evolve: consider Teams
- You want to direct delivery yourself and need particular expertise or additional capacity: consider Specialists

How it runs:
1. **Define the work**: We review the objectives, requirements, existing material and constraints. Where further scoping is needed, we agree that work before pricing the project.
2. **Agree scope and price**: We agree the scope, fixed price, milestones and acceptance criteria, together with the responsibilities and decisions needed on each side.
3. **Deliver and review**: We manage delivery and review progress and completed work with you regularly. Risks and proposed changes are raised early, with their effect on scope, cost and timing explained.
4. **Accept and hand over**: We review the deliverables against the agreed criteria, address any acceptance issues and complete the documentation and handover specified for the project.

- **Do we need a workshop, and is it charged separately?** We first review the scope and material you already have. If further definition is needed, we propose a scoping workshop before giving a fixed price. The workshop is a separate, paid engagement with its own deliverable. Any project that follows is scoped and priced separately.
- **What does the fixed price include?** The proposal identifies the deliverables and the work required to produce them, including the roles and coordination needed for that scope. It also sets out assumptions, acceptance criteria and any costs or responsibilities outside the price.
- **Can you take over an existing project?** Yes, where the remaining work can be assessed and defined. We review the existing software, documentation and dependencies before agreeing the scope and price for the work we would take on.
- **What happens if the requirements change?** We assess the proposed change and explain its effect on scope, price and timing. You can approve it, exchange it for other agreed work where practical, or leave it for a later phase. We record the agreed decision before the changed work proceeds.
- **What if the delivery date needs to change?** We explain the cause and its effect on the plan as soon as it becomes clear. We discuss the options with you and document any agreed change. The commercial treatment follows the project agreement and the reason for the change.
- **How do acceptance and payment work?** The project agreement defines the milestones, acceptance criteria and payment schedule. We review completed work against those criteria and address any acceptance issues through the agreed process.
- **Who owns the work produced?** You own work produced for the engagement under our agreement. Code, designs and documentation are delivered through the repositories and tools agreed with you.
- **What happens after delivery?** The agreement sets out the handover, any warranty or defect-resolution period, and any support included after delivery. Ongoing support or further development can be agreed separately.

---

Published by Extra.dev (https://extra.dev), a software engineering team in Ljubljana, Slovenia.
Canonical page: https://extra.dev/engagement/projects
Contact: hello@extra.dev · Replies within one working day
Site index for agents: https://extra.dev/llms.txt · Full text: https://extra.dev/llms-full.txt