Skip to content
Help speed up the development
AI-powered analytics

Getting insights from your data shouldn’t feel like a full-time job.

Skip the technical grind. Upload your data, ask questions, and explore what matters. Tuklasin handles the rest.

A preview of what your workspace could look like. The product is still in development.

Project

North Revenue Decline

North Revenue Decline

Updated 2 hours ago
Goal

Understand why revenue in the North fell after the July wholesale policy change.

Key metrics
Revenue₱470kdown 9.6%
Orders18,442up 0.4%
Avg. discount18.4%up 4.2 pts
Avg. order₱25.50down 10.1%
Main trendRevenue trend

North net revenue, monthly

Actual
560k420k280k140k0kJANFEBMARAPRMAYJUNJULAUGSEP

Three straight months down after a year of growth — the break lines up with July.

What stands out?

Revenue broke trend in July

Three straight months down after a year of growth, and the break lines up with the wholesale discount policy rather than with demand.

Units held while value fell

Order sizes barely move between the two clusters. Only price does — which is what rules out a demand explanation.

Recent findings
Ask about this project

What am I looking at?

Revenue down 9.6% since July while orders held flat. The gap between those two is the whole story — it is price, not demand.

Which of these should I look at first?

The July break. It is the larger of the two, and the only one with something behind it you can reverse.

Ask a follow-up
How it works

Three steps, from a spreadsheet to a decision

The same path every time, so you always know where you are and what happens next.

01

Upload or connect data

CSV, Excel, or a SQL database. Tuklasin reads it the moment it lands — columns, types, missing values, and the problems worth knowing about before anyone acts on them. Preparation happens underneath; what comes back is something your team can read.

SOURCEREAD ON ARRIVALCSVXLSXSQLCOLUMNTYPEdatenumtextint2 PROBLEMS FLAGGED
02

Ask what you want

A business question in your own words, with no method to choose. Tuklasin also proposes investigations you would not have thought to ask for, each with the reason it came up — and nothing runs until you pick it. You can reject the reasoning, not only the result.

YOUR WORDS, NO METHODPROPOSED, WITH REASONSWHY: JULY BREAKWHY: 31 SLOWEDWHY: 6.5% MISSING
03

Tuklasin analyzes and explains

Churn, demand, margin, the transaction that does not fit. The method is chosen, tuned and validated for you, then named on the record. The engines compute it with visible progress — the stage it is on, and how long is left — and the finding comes back in plain language, with its warnings and what to look at next.

VISIBLE PROGRESS~40S LEFTREADFITCHECKSCOREWRITEFINDINGCAVEAT ATTACHED
Principles

Rules the product holds itself to

Analytical tooling is easy to make confident and wrong. These are the constraints that keep it honest.

Sheet 01 of 06
01Doc TK-100 · Rev A

You don’t need to speak data science

Which statistical test, which algorithm, which validation strategy — none of that is a question you have to answer. The default experience is business language; the technical detail is there when you want it, and out of the way when you don’t.

02Doc TK-100 · Rev A

The AI never does the math

The language model reads, recommends, and explains. Every statistic, metric, and prediction is computed by a dedicated analytical engine. A number the model produced by itself would be a bug, not a result.

03Doc TK-100 · Rev A

Nothing runs until you choose it

Recommendations are proposals. The system does not quietly run everything it can think of and present you with the winner.

04Doc TK-100 · Rev A

Every recommendation explains why

A suggestion offered without a reason is incomplete. You should be able to disagree with the reasoning, not just the result.

05Doc TK-100 · Rev A

Results ship with their warnings

Class imbalance, missing data, weak statistical evidence, overfitting, data leakage. The caveat travels with the finding instead of living in a panel you can skip.

06Doc TK-100 · Rev A

Every investigation is a reproducible record

What ran, on which data, with which method and validation, and what it found — kept so any result can be found again, compared, and re-run.

Who it’s for

Business people who need deeper analysis — not another technical job

You’re a marketer, operator, finance lead, customer success manager, or founder. You know your business. You know what questions matter. You shouldn’t have to become a statistician or data scientist just to answer them.

Tuklasin handles the complexity while you stay in control of what you want to investigate.

Sales

Pipeline, stage by stage

Marketing

Channels and what they return

Finance

Margin, drivers, outliers

Operations

Where the queue builds

Customer Success

Retention, and who slips

Find out what your data already knows

Upload your data. Let Tuklasin make sense of it. Discover what matters, choose what to investigate, and understand what it means.

See how it works
FAQ

How the product actually works

No. You bring the business question; which method answers it is decided for you and explained in plain language. The technical detail — the method, the validation strategy, the metrics — is available whenever you want to inspect it, but you are never required to understand it to use the product.

From analytical engines, never from the language model. The model decides what is worth investigating and explains what came back; the computing happens in dedicated statistical and machine-learning code. Every number can be traced to the run that produced it.

No. It reads your data automatically and recommends investigations automatically, but nothing executes until you select it. Recommending and running are deliberately separate steps.

Yes. Every investigation is stored as a reproducible record — the dataset and version, the question, the method, the validation strategy, the results and the warnings. Records can be compared against each other and re-run. Nothing is a black box you have to take on faith.

You see where it actually is — the current stage, the analysis being run, cross-validation progress, results so far, and an estimate of the time remaining. An indeterminate spinner is not considered acceptable.

Not yet. A workspace is for one person today — there is no sharing, no second seat, and no roles. “Teams” describes who Tuklasin is built for and whose questions it answers, not how many people can be in it at once. Working together on the same data is a direction we are interested in, not something we are promising.

That is the intended use. Every recommendation states its reasoning so you can reject it on the merits, and you stay in control of what runs, what gets revisited, and what gets ignored.