Solve · Data
The weekly numbers live in two or three systems and a spreadsheet that holds them together. Every week somebody exports, pastes, fixes the columns that moved, and sends it before the meeting. J Labs builds the step that pulls the numbers, calculates them the way your team already calculates them, and delivers the report on a schedule.
Summary
J Labs automates recurring reporting for teams whose weekly numbers are assembled by hand from two or three systems and a spreadsheet. The sources are connected, the calculation your team already does is reproduced exactly rather than improved on quietly, and the report is delivered on a schedule to wherever people already look, an inbox, a channel, or a dashboard. The work that makes it trustworthy happens before any of that: the definitions get written down and agreed. What counts as a sale, which date a figure belongs to, how a refund or a credit note is treated, and which records are excluded. Where sources disagree the report says so rather than silently preferring one, and when a run fails a person is told instead of an empty report going out looking like a bad week. For a Danish quantity surveying firm, procurement data across 6 countries was standardised in a six-week cleanup phase before a reporting layer was built on top of it, which is the usual order. Engagements are fixed scope, fixed timeline and fixed price, from the Spec at €5,000.
What we automate
The numbers read from the systems they already live in on a schedule, rather than somebody downloading a CSV and pasting it into the sheet that holds the formulas.
The arithmetic your team does today, written down and then built. If we think a definition is wrong we say so and you decide; what we do not do is quietly improve it and hand you a report whose numbers moved for no visible reason.
What counts, which date it belongs to, how refunds and credits are treated, what is excluded. This is the part that decides whether anyone believes the report, and it is the part that gets skipped.
Where two systems give different answers the report says which and by how much, instead of picking one and looking confident. A number nobody can reconcile is worse than two numbers you can see.
If a source is down or a field changed shape, a person is alerted. An empty or partial report arriving on time looks like a quiet week, and that is how a reporting system starts lying.
An inbox, a Slack or Teams channel, or a dashboard. A report that needs a new login to read is a report that stops being read in three weeks.
Fit
This is for you if
The report already exists and somebody builds it by hand. That is the ideal case. The calculation is known, the audience is known, and the value is the morning it takes back every week.
The numbers live in systems with a way in. Two or three sources with an API or a scheduled export. If one of them is a system with no documented way in, we will tell you on the call rather than after you have paid.
Somebody can settle the definitions. One person who can say what counts as a sale and have that stick. That is the shape the Spec covers: specified, built and tested for a fixed price.
This is not for you if
You want a data warehouse first. You very likely do not need one for this. A warehouse is the right answer for some problems and it is a long way round for a weekly report off two systems.
The definitions are genuinely contested. If two departments disagree about what a sale is, automation will not settle it; it will just produce the disputed number faster and more often. Settle it first, which is a useful conversation on its own.
You want the report to interpret itself. We will deliver the numbers and flag what changed. What it means, and what to do about it, is the meeting. A generated narrative over data nobody has agreed on is confident noise.
Systems
The ones you already run. We don't insist on rip-and-replace: the automation layer goes on top of the systems in place, and if a system is genuinely past saving we say so on the discovery call and show our working.
Engagement options
| Engagement | Price | Timeline | What you get |
|---|---|---|---|
| The Spec | €5,000, fixed | Fifteen working days | One clearly defined outcome, designed, built and tested: two sources, the agreed definitions, the calculation reproduced, scheduled delivery and a failure alert. A free assessment confirms it fits before you pay. |
| Reporting layer build | Fixed price, quoted after discovery | Typically four to eight weeks | The report plus the foundation under it: the data cleaned and standardised, one trustworthy source stood up, and the reporting and alerting built on top of it. |
| Bespoke | Multi-phase, to €200,000+ | Multi-month, phased | A data layer across entities, countries or currencies, where the cleanup is the project and the reporting follows it, phased with weekly check-ins. |
None of these is an off-the-shelf product. There is no J Labs software to install: every system is specified in the brief, built for your stack, and owned by you. Every engagement is fixed scope, fixed timeline and fixed price, with acceptance criteria agreed before work starts. See how we work and the Spec.
What we've shipped
Quantity surveying · 6 countries
Procurement data standardised across 6 countries in a six-week cleanup phase, with a pricing intelligence layer built on top of it.
The product that fixes it
The Spec · 5,000 EUR
Two sources, a calculation that already exists on paper and scheduled delivery is the textbook Spec: the definitions get written down with you, then the thing gets built and tested against them.
Live availability
Live slots from our team calendar, weekdays, European working hours. A 20-minute intro or a 45-minute working session, your choice, on Google Meet. You get a one-page summary within 24 hours.
How much time do you need?
Step 1 · Pick a date
Loading availability…
Frequently asked
Or start with our brief templateWe reply within one business day.