TouringXX
ES EN
Request an assessment

Intelligence and automation

Enterprise AIFeatured AI HubPlatform · featured Chatbots and conversational agentsWeb · messaging · voice Automation and integrations Internal apps and systems AI avatars and digital twins

Web and product

Web design and development E-commerce development Performance and optimisation Maintenance and support

Visibility and marketing

SEO, GEO and AI visibility Marketing, content and social media

Brand and production

Design, print and production Branding and visual identity Problem solving & technical fixes

Not sure which service you need?

Tell us your goal and we will propose the next step.

Request an assessment
The process

A clear process to define, deliver and validate every project.

Eight stages grouped into three blocks — strategy, implementation and continuity — the same across all sixteen services, with each one’s own variations. The current methodology rests on more than two decades of experience solving projects of different sizes and levels of complexity.

The four commitments
Scope in writing. Before the first billed hour, with the list of what falls outside.
Fixed price or declared ceiling. You know the maximum before starting, not when the invoice arrives.
Everything in your name. Access, domains, accounts and code stay under your ownership.
Documentation on delivery. Enough for another team to continue without us.
The contractual details — payments, revisions and responsibilities — are defined in each project’s proposal.
At a glance

TouringXX works with an eight-stage process grouped into three blocks: strategy (discovery, assessment, strategy and proposal), implementation (design and build, validation and launch) and continuity (support and evolution). Before starting, what is included, what isn’t, how many revisions and what timings apply are all defined in writing. Each phase ends with a concrete deliverable the client approves before continuing. The goal is for the client to be able to maintain the result without depending on the studio. The process rests on more than 20 years of experience on projects of different scales, for companies and entrepreneurs.

Early decisions define the result

More than two decades of experience make it possible to recognise which decisions are better taken early, which aspects need validation and where complexity usually appears during a project.

That is why the scope is defined in writing at the start: what is included, what isn’t, how many revision rounds and what timings. It is the basis for later decisions to be taken with judgement rather than under pressure.

Written scope Approval per phase Fixed price Documented delivery No lock-in
The process

Eight stages, three blocks, each stage with its own close

No stage starts before the previous one is approved. That makes disagreements appear early, while correcting is still cheap.

Strategy Stages 1–4

Understand the problem, decide the approach and put the scope in writing before producing anything.

Implementation Stages 5–7

Build, validate against agreed criteria and go live with a full handover.

Continuity Stage 8

Support what was delivered, fix what appears in real use and decide the next evolution.

01

Discovery

Strategy

A long conversation and a review of what already exists: systems, materials, project history and who decides. The aim is to gather context, not to propose yet.

Duration: 1 week Initial session at no cost
You receive
· Summary of the context gathered · List of relevant systems and materials · Open questions that need resolving
What we need from you
· An initial session of 45–60 minutes · Read-only access to whatever exists · Who decides on the client side
02

Assessment

Strategy

The analysis of what was gathered: what is failing, what is cause and what is symptom. The real problem is almost never the one stated first.

Duration: 1–2 weeks Depending on depth
You receive
· Document with the problem defined · Priorities and risks identified · What to resolve first, and why
What we need from you
· Clarifications on whatever appears · Access to data or metrics if they exist · Validation of the problem as stated
03

Strategy

Strategy

The decision on approach: what options exist, what each implies in time and budget, and which one we recommend, with the reasoning.

Duration: 3–5 days At no cost
You receive
· Possible options with their order of magnitude · A reasoned recommendation · The criteria success will be measured by
What we need from you
· Real constraints on timing and budget · Business priorities · A decision on the approach
04

Proposal

Strategy

The scope written out in detail: what it includes, what it doesn’t, how many revisions, with what timings and under which billing model.

Duration: 3–5 days At no cost
You receive
· Detailed scope with exclusions · Schedule with approval milestones · Budget and payment terms
What we need from you
· Review and questions on the scope · Confirmation of internal dates · Signature to begin
05

Design and build

Implementation

The work itself, divided into partial deliveries. Each delivery is reviewed and approved before moving to the next.

Duration: Depending on scope Per the proposal
You receive
· Reviewable partial deliveries · Progress report at each milestone · Access to the working environment
What we need from you
· Response to reviews within the agreed window · The materials and content committed · A stable point of contact
06

Validation

Implementation

Checked against the criteria defined at the strategy stage: functionality, performance, accessibility and behaviour on the agreed devices and browsers.

Duration: 3–7 days Included
You receive
· Record of tests and fixes · Accessibility and performance review · List of what falls outside scope
What we need from you
· Review by the client’s team · Validation of the real use cases · Approval to publish
07

Launch

Implementation

Going into production, handover of access and documentation. This is where the project ends and the client’s autonomy over what was delivered begins.

Duration: 1 week Included
You receive
· Everything published and working · Access and source files in your name · Documentation and a handover session
What we need from you
· Final validation of the result · People from the team for the handover · Confirmation of closure
08

Support and evolution

Continuity

A warranty period to fix whatever appears in real use and, if the project continues, decide the next iteration with usage data in hand.

Duration: 30 days included Afterwards, per plan
You receive
· Bug fixes at no cost · Support for questions about use · A maintenance or evolution proposal
What we need from you
· A report of whatever appears · A decision on continuing or closing · Nothing else
Budgets

How each type of work is quoted

Not everything can be quoted the same way. A site with a defined scope is budgeted at a fixed price; research whose result isn’t known in advance is not. Choosing the wrong format is what later generates billing disputes.

The proposal states which model applies and why that one rather than another.

ModelWhen it is usedHow it is billed
Fixed price The scope can be defined precisely: a site, an identity, a specific integration. By approved milestones.
Maximum ceiling The scope is clear but the effort varies: a technical rescue, a migration. For work carried out, without exceeding the agreed ceiling.
Bounded iteration The result isn’t known in advance: research, AI exploration, proofs of concept. Closed blocks with a review at the end of each one.
Monthly retainer Ongoing services: maintenance, support, recurring content production. Monthly, with a defined monthly scope and agreed renewal.
Amounts aren’t published because they depend on the real scope. What is fixed is the principle: once signed, a fixed-price proposal doesn’t change price unless the scope changes in writing.
The hard cases

What happens when something goes wrong

It is worth knowing before starting. These are the answers, in writing, to the four situations that happen most often.

Situation

What if we run past the date?

If the delay is ours, nothing extra is billed and we adjust the schedule as soon as we spot it, not on the due date. If the delay comes from materials or approvals pending on the client side, it is rescheduled and logged, because it usually drags the rest of the calendar with it.

Situation

What if the result doesn’t convince us?

We use the revision round that corresponds to that phase. If the disagreement persists after that, it almost always means something was poorly defined in the proposal; in that case we review the scope together and decide whether to correct it or whether stopping is better. We would rather close a project well than drag it along.

Situation

What if we want to cancel halfway?

You can. We bill the work carried out up to the last approved delivery and hand over everything produced to that point, with its access and files. There is no cancellation penalty and no withholding of material as payment security.

Situation

What if something nobody foresaw comes up?

We stop, explain it and decide together before spending time on it. Unforeseen work is never carried out and billed afterwards. If it is minor, it is usually absorbed; if it changes the scope, it is quoted separately and the client decides whether it goes ahead.

Revisions

What counts as a revision and what counts as a change of scope

This distinction is the source of ninety per cent of arguments on creative projects. That is why it is defined before starting, with examples rather than an abstract formula.

Included Revision

Adjusting what was delivered within what was agreed: changing a text, moving a module, correcting a colour, refining a behaviour. Each phase includes a defined number of rounds.

Quoted Change of scope

Adding something that wasn’t there: a new section, another language, an integration that wasn’t listed. It isn’t a problem; it is simply quoted before being done.

No cost Bug fix

Something delivered that doesn’t work as agreed. It consumes no revision rounds and isn’t billed, inside or outside the warranty period, if the fault originates with us.

What we always deliver
Signed scope document, with explicit exclusions.
Access, domains and accounts in the client’s name.
Editable source files, not only the final result.
Technical documentation of what was built.
Recorded handover session with the client’s team.
Record of the decisions taken during the project.

Whatever the service. A job without delivered documentation isn’t finished, even if it works.

On the process

“Responsive, kind, patient and with great communication skills (that is, a good listener when it comes to the details the client asks for). I would like to work with this professional on future projects.”

mm
mmpaevans · Client review
Original wording · source: Envato Studio
What can be claimed

An orderly process reduces risk; it doesn’t remove uncertainty.

Some things don’t depend on us: material arriving late, an internal decision getting stuck, a requirement appearing halfway through. What this process guarantees is that those situations are spotted in time and resolved with a conversation, not with a surprise invoice.

View all testimonials
Frequently asked questions

Questions about hiring and working together

The ones that come up while reading a proposal, before signing it.

Does the assessment cost anything?+
The initial conversation and the general recommendation are at no cost. When the assessment requires auditing systems, reviewing code or analysing data in depth, that is work in itself and is quoted; in that case the amount is credited if the project is then contracted.
How much does a project cost?+
It depends entirely on the scope, which is why we don’t publish rates: a reference price without knowing the problem is an invented figure. What we can do in the first conversation is give an order-of-magnitude range, so you know quickly whether we are on the same map.
How is payment handled?+
By approved milestones, not by time elapsed. We never bill the whole project in advance, and we never withhold delivered work as payment security.
What if our team is slow to respond?+
We flag it as soon as it affects the schedule and reschedule by mutual agreement. It is the most frequent cause of delay on any project and carries no penalty, but it does have a consequence for dates: if an approval takes two weeks, the delivery moves.
Do you work with a contract or an informal agreement?+
Always with a signed contract, even on small jobs. It isn’t distrust: it is what makes both sides know where we stand if something changes. The contract records the same things this page says.
How many people work on my project?+
Between two and four, depending on the service, and there is always a stable point of contact. We don’t rotate the team mid-project except in exceptional circumstances, and if it happens we say so beforehand, not after.
Can we start with something small and grow?+
Yes, and it is usually the best way to start working together. A first bounded job lets both sides see how the relationship works before committing to a large project.
What happens to what was delivered if we stop working together?+
It is yours, unconditionally. Access, code, files and documentation are in the client’s name from the moment of delivery, not at the end of the relationship. Changing vendor requires negotiating nothing with us.

Keep exploring

You know how we work; what’s left is what we do and who with.

To go deeper

On scope, estimates and why projects run past their date.

The quote is finalised at the proposal stage. The factors that determine the amount are explained separately.

See what shapes the budget →

Let’s start with phase one: the assessment.

An initial session of 45 to 60 minutes about what you need to solve, and a short summary with the conclusions, the options and their order of magnitude. With no commitment to continue.