Start from the decision
Every data artefact must connect to one decision we can name. If it does not, it is probably not worth doing.
Four years working behind the scenes for Indonesian companies: tidying data, agreeing on definitions, and training the people who will use them.
Before founding RaspberryFla in 2022, the three of us worked in the data teams of different companies and faced the same problem every month: the numbers we reported were always questioned. Not because the calculations were wrong, but because every division had its own definition and there was no single place that could be called the source of truth.
We decided to fix the root cause: written metric definitions, pipelines whose results can be challenged, and users involved from the design stage. We prioritise impact on net profit over simply adding to the data warehouse.
Today we are a team of 18 people with a mix of analytics, data engineering, and industry backgrounds. We hold to one rule: if a data initiative is not connected to a decision we can name, we recommend putting it on hold.
"We measure success by decisions that change, not by the number of dashboards built."
Rangga Prasetyo — Founder
Started by three people tired of watching monthly reports assembled by hand from a dozen spreadsheets.
Focus shifted from reports to foundations: data warehouse, modelling, and agreed metric definitions.
Formed a dedicated governance & data quality team after the need for consistent definitions across units kept recurring.
The first forecasting model entered the daily production planning process and now runs without manual intervention.
The team grew to 18 people based in Jakarta, collaborating across cities.
140+
Analytics projects
since 2022, across 9 industries
9
Industries understood
retail, FMCG, finance, public
4 years
Years in practice
since 2022 in Jakarta
96%
Dashboard adoption
weekly active users
Every data artefact must connect to one decision we can name. If it does not, it is probably not worth doing.
We report unwelcome results sooner. Including when a project should be stopped.
Success is measured by your team's ability to maintain the solution after we finish.
The cheapest solution that solves the problem comes first. Complexity is added only when it is proven necessary.
Every stage has an output that can be read and approved. There is no jumping straight to technology.
We sit down with the owners of the business problem, not just the IT team. The goal is one thing: define the question worth answering with data and estimate its value.
We audit data sources, quality, access, and infrastructure readiness. The output is an honest list of gaps, including what cannot be done yet.
Architecture, data models, metric definitions, and user experience design come together into one blueprint we approve together.
Iterative work in two-week sprints. Every iteration produces value that real users can see and test.
Documentation, training, and coaching until your internal team can run and extend the solution on its own.
Senior consultants are involved from day one.
Founder & Principal Consultant
16 years building data architecture for banking and retail. Previously led the data team at a national banking group.
Head of Analytics
Built the analytics function from scratch at two e-commerce companies. Specialist in experiments and incremental measurement.
Lead Data Engineer
Writes pipelines that do not scream at midnight. A firm believer in automated data testing and observability.
Data Governance Lead
Bridges regulatory compliance and business needs, including implementation of Indonesia's Personal Data Protection Law.
Plus 14 consultants, analysts, and data engineers working across projects. We are opening several positions — send your profile to official@raspberryfla.web.id.
Still something on your mind? We are happy to answer by email.
An assessment and the first dashboard usually take 6-10 weeks. Data engineering or machine learning projects typically run 3-6 months and are split into two-week iterations.
No. About a third of our projects start from spreadsheets and operational databases. We design a phased path so infrastructure investment happens only when it is genuinely needed.
Common options: fixed scope for an assessment, a monthly retainer for ongoing support, or a dedicated squad for continuous development. All of them are transparent about hours and outcomes.
Absolutely. We work alongside your team in one workflow, with code reviews and weekly knowledge-transfer sessions. Without that, the solution will not last.
We sign an NDA, use isolated working environments, and apply data minimisation. For personal data, our approach follows Indonesia's PDP Law and GDPR practices.
Tell us about your current data situation. We will give you an honest view of what is worth doing first.