explōrātiō takes your files as they are today — platform exports, spreadsheets that grew at the edges, systems that do not talk to each other. You get back a single base with written rules and a dictionary, ready for your team to use on Monday — without spending all of Friday on “cleaning the table for the meeting.”
Input → processing → output
What goes in, what runs in the middle, what you take away — and the project timeline below.
From contract to close-out
You send files in whatever format you have today. We agree in writing what needs to happen — dedupe rows, standardize campaign names, merge two sources, calculate margin, and so on — and return a ready base with documented rules, so your team’s next step does not depend on guessing what was done.
From marketing to data, everyone loses hours stitching files together, renaming columns, merging platform exports. Here that work becomes a one-time delivery — with written rules and a base ready for the next use, without becoming the fourth parallel spreadsheet nobody knows is official.
Each platform, each client, each publisher delivers reports in a different format. Here everything becomes a single model, with taxonomy and field names documented — ready to feed the dashboard, MMM, or client report without the intermediate step of “let me just standardize first.”
Models, dashboards, and pipelines need clean input. You get a field dictionary, written transformation rules, and an agreed output format — so your team stops carrying business rules only in the head of the analyst on vacation.
Value recalculation, harmonization across sources, and adjustments that support the next model — with process documentation so the next round does not start from zero. Delivered the way your team integrates: CSV, SQL, Parquet, whatever is in scope.
Whether the package is Light or Enterprise, delivery has four fixed elements. What changes between packages is size — number of sources, rows, and rules — not the shape of the delivery.
Final consolidated file in formats agreed in scope — CSV, XLSX, SQL, Parquet, or other. Ready to open in Excel, import into BI, or ingest into the pipeline, without the intermediate step of “I need to convert first.”
Each column in the base has: technical name, business-language description, data type, fill rule, and examples. No more “what does this field mean again?” three months after delivery.
Everything done to the base — what was removed, merged, recalculated, renamed — is listed and explained. Auditable by whoever arrived later, repeatable by your team if the next load comes in the same format.
After delivery, 15 to 30 days (depends on package) for one consolidated round of adjustments. Anything after that, or in a second round, is treated as new scope — no gray zones, no “just one more thing” becoming habit.
Billing by hours worked hides what was done and opens the door to endless project growth. Here the model is different: scope fixed in writing, price fixed before starting, delivery defined before execution. You know exactly what you will receive, how long it will take, and how much it costs — before the first line of code runs.
Each scenario describes a concrete situation — media team with five platforms, dashboard that breaks on every load, SMB trying to close the month — what was happening before and how the package arrives to solve it. Illustrative scenarios, based on typical market cases.
Illustrative scenarios · based on typical market cases
Four packages as one-time delivery. What changes between them is size — how many sources, rows, and transformation rules. In the initial conversation we look at a sample of your base and indicate which package it fits; if it sits in between, we choose the smaller one and treat the excess as an add-on.
R$ 3.947
R$ 5.947
R$ 13.947
R$ 19.947
For agencies that want to deliver Data Clean under their own brand, and for data teams that want the package in the technical standard they integrate, specific formats by conversation. WhatsApp · reply within 1 business day.
Data work is about scope, and scope sometimes changes — a new source appears, an extra field enters, a calculation rule needs adjusting. Instead of hiding the rule, we put the table in plain sight: what triggers an add-on, what becomes new scope, and what each case costs on top of the contracted package.
+35%
Change up to 25% of signed scopeOn the initial signed package value. Ex.: Light package (R$ 3.947) → increase of R$ 1.381.
+50%
Change above 25% of scopeChange above 25% of signed scope. Ex.: Light package (R$ 3.947) → increase of R$ 1.974.
25%
Limit by transformation rulesEx.: Light package — 10 transformation rules in scope. Request changes 2 rules (20% of scope) → targeted add-on (+35%). From the 3rd rule changed (≥30%) → broad add-on (+50%).
25%
Limit by fields impactedEx.: Light package — 20 fields in scope. Request impacts 4 fields (20%) → targeted add-on (+35%). With 5 fields (25%), still targeted; from the 6th field impacted (≥30%) → broad add-on (+50%).
15–30d
One round after formal deliveryRequests consolidated within the deadline. Written sign-off (email counts). After that = new scope.
New
Outside add-on — quoted separatelyDifferent base, period, or dictionary; calculated field outside what was agreed; format not foreseen; request after the window.
Criteria A and B measure the % of scope changed · higher index prevails · targeted add-on +35% or broad +50% on the package · all within signed scope
Reference clause in scope: the client has 15 to 30 calendar days after delivery to request adjustments, in a single consolidated round. Requests after that deadline, or in additional rounds, will be treated as new scope and quoted separately.
The initial conversation is to look at a sample of your base and say frankly: there is Data Clean here that solves it, which package it fits, or your team can still handle it alone. If yes, we close scope, timeline, and format on the spot. If not, you leave with the diagnosis anyway.
Fixed package, within signed scope. Usable the day after delivery, auditable by whoever arrived later, with written sign-off. No “almost ready,” no endless revision round, no delivering half.