Paradigma7

Every service · one delivery standard

What we do and how we deliver it

Seven areas of work, one delivery standard: a written proposal, a private repository under our control, tests, documentation and a 12-month warranty.

7
areas of work
12
month defect warranty
17
years of experience
EU
data hosting

The part that never changes

Whichever service you pick, these are always there

Price and timeline change with the project; the way we work does not. The six points below are part of the contract on all seven services.

  • A written, numbered proposal

    Scope, assumptions, delivery plan and price in one document. We never start work on a verbal agreement.

    On all seven services

  • A private repository under our control

    The code sits in a private GitHub repository controlled by Paradigma7 from day one; complete, maintainable source code is handed over at delivery.

    On all seven services

  • Automated tests

    Critical flows are covered by unit and end-to-end tests; every delivery reaches you through CI.

    On all seven services

  • Documentation and training

    Setup, operations and admin use are written down, then walked through with your team in a live session.

    On all seven services

  • 12-month defect warranty

    Defects found after delivery are fixed at no cost, with response times written into the contract.

    On all seven services

  • Hosting inside the EU

    Data stays within the European Union; GDPR compliance is designed in from the start.

    On all seven services

Process

How an engagement actually runs

Five steps from the first call to the warranty period. Each step leaves something in writing, so you never have to guess where things stand.

  1. Day 1

    01

    Intro call

    45 minutes on the need, the systems you already run and the budget range. If we are not the right fit, we say so on that call.

  2. 3–5 days

    02

    Proposal and scope

    You receive a numbered proposal with scope, assumptions, delivery plan and a fixed price.

  3. Week 1

    03

    Contract and kickoff

    Contract, repository, environments and your client-portal account are set up; communication moves to one channel.

  4. Every two weeks

    04

    Build and demo

    We work in two-week cycles. Every cycle ends with a working build and a short demo.

  5. Launch + 12 months

    05

    Launch and warranty

    Release, training and handover, followed by a 12-month defect warranty and defined support times.

Frequent questions

What clients ask before the proposal

Something else on your mind?
How do you set the price?

Once the scope is clear we quote a fixed price. If the scope is still open, we suggest a short paid discovery first — its output is yours to keep, wherever you go next.

What is your minimum engagement?

We generally do not take on projects shorter than four weeks. For smaller needs we offer standard support during working hours and an annual maintenance agreement.

Who owns the code?

You do. When payment is complete, the source code, design files and every account are transferred to you. We never leave you locked into us.

Will you take over an existing project?

Yes. We start with a one-week code and infrastructure review and hand you the risks and the cost of taking it over in writing. You are free to stop there.

Which languages do you work in?

Turkish, English, German, Italian, French, Dutch and Spanish. Contract, documentation and weekly calls all run in the language you choose.

Is 24-hour support included in every project?

Standard support runs during working hours. For large projects, a dedicated 24-hour support package is offered separately.

Does the annual maintenance agreement include 24-hour support?

The annual maintenance agreement does not by itself mean 24-hour support. The support scope and any dedicated package terms are set out separately in the agreement.

Are the 12-month warranty and annual maintenance the same service?

No. The bug-fix warranty covers defects in the scope that was delivered. What annual maintenance covers is defined separately, and new features are planned separately.

Not sure which service you need?

A short call usually settles it. Tell us what you are trying to do and we will pick the right starting point together.