Technical specification

Effective date: 20.08.2025

A Technical specification (TS) is a clear, non-technical blueprint that outlines everything included in your software project - features, structure, roles, and timeline.

It protects both sides, aligns expectations, and ensures smooth delivery from planning to launch.

What is a technical specification?

A Technical specification (TS) is a structured document that describes exactly what will be built during your project. We write it ourselves in simple, non-technical language, so it’s easy to understand for everyone - not just developers. It’s the blueprint for the system, defining how it will look, what features it will include, and how everything is organized.

This document serves both as a planning guide and a mutual agreement - helping to prevent scope misunderstandings, technical surprises, or budget overruns.

Why both sides need it

  • For you (the Buyer): The TS gives full clarity - what’s included, how it works, what the project will cost, and when each part will be ready.
  • For us (the Developers): It gives us a fixed and approved scope to work from, reducing risks and ensuring predictable delivery.
  • For both: It creates alignment, avoids vague assumptions, and provides a permanent reference point throughout the project.

How much does it cost?

The Technical Specification is a paid service priced at 5-7% of your estimated project budget, depending on project complexity.This fee is separate from and not included in the development price (it is not deducted from the project total).

Example:
If your forecasted budget is €20,000 - the Technical Specification costs €1,000 - €1,400 (5-7%).
This amount is billed independently and is not credited toward development fees.

How we write the technical specification

We handle the full process and guide you through it with easy questions, examples, and recommendations. Here’s what we typically do:

  • Gather information through a short discovery session (or document)
  • Analyze your goals, user types, content, and any references you provide
  • Write everything in plain language, not developer jargon
  • Create a clear feature list and system structure
  • Draw layout wireframes to visually explain what each page or section does
  • List out user roles and permissions in a way that makes sense
  • Plan how the project will be split into milestones
  • Suggest technologies or platforms based on your goals (not trends)
  • Include examples and screenshots where helpful

You don’t need to prepare anything technical. Just tell us what you want to achieve, and we’ll turn it into a solid plan.

Topics covered in the TS

Here’s a breakdown of what the document includes:

1. Project overview

What we’re building, why, and for whom

2. System structure

Tech stack suggestions, hosting notes, and localization needs

3. Feature set

All functions grouped by section: what each part does and who can use it

4. User roles

Admins, managers, visitors, etc. - what each one can access and manage

5. Sitemap and interface list

Pages, sections, and how users will navigate between them

6. Wireframes or layout notes

Simple sketches to show what key pages and blocks might look like

7. Milestone plan

Project divided into phases, each with its own timeline, scope, and quota

8. Integrations

External services, APIs, payment gateways, or plugins that will be connected

9. Out-of-scope areas

Clarifies what’s not included unless specifically agreed (e.g., SEO, content writing)

10. Post-launch

Notes on delivery, warranty, and optional support coverage

Ownership and confidentiality

Until the project is completed (delivered and fully paid), the Technical Specification and all drafts remain the Agency's intellectual property.

  • We grant you a non-transferable, read-only license to review the document internally for decision-making.
  • You may not share, publish, distribute, or send the document (in whole or in part) to other companies, vendors, or third parties without our prior written consent.
  • Any reuse of the Technical Specification outside our engagement requires a separate written license or buyout agreement.

Wrapping up

The Technical specification is the first and most important step of any successful project. It protects both sides, builds trust, and sets a strong foundation for development, testing, and delivery.

It’s a smart investment that pays off by eliminating confusion and saving time later.