Modular Products
i-spark configures Claude Code into your dbt and Power BI environment, governed from the start, tested against your actual setup, and handed over so your whole team can use it from day one.
For those that don’t have Claude Code connected to their data stack, i-spark configures it properly, governed from the start, and hands it over in one day.
A quick local install produces generic output — DAX that references tables you don’t have, models that don’t know your sources exist. Someone with deep technical knowledge ends up editing AI drafts rather than being unblocked by them. The tool adds a step instead of removing one.
And here's the thing, it guesses pretty well. The output looks completely fine. It looks like something a competent engineer wrote on a Tuesday afternoon.
So you take it, you try to use it, and then it starts breaking. Table names that don't exist in your project. A date table structure that doesn't match yours.
And you're sitting there thinking, okay, who has to fix this? It's the one person on the team who knows the codebase well enough to spot what's wrong, the same person who could have written it correctly in the first place.
It knows your tables, your sources, the relationships you've defined, and the tests you've already written. So when you ask it to generate a new staging model, it's looking at what you've already built and working within that.
Same with DAX. A measure for revenue year-over-year will reference your actual date table, your actual sales table, the relationship between them as it exists in your model. The output is specific.
And when something is specific, people across the team can read it, verify it, and use it.
Not a generic install. The configuration is validated against your project before handover. You don’t inherit a setup that works in theory.
Credentials stored securely, rotation documented, ownership assigned. The Power BI connection is more credentials-sensitive than most teams expect, we handle this at setup, not as an afterthought.
The MCP server configuration lives in the repository alongside everything else. The next person who joins knows how to use it. No tribal knowledge required.
You end the day with a walkthrough. The setup is yours, there is no ongoing dependency on i-spark. You own it completely.
The connection changes what’s possible for everyone on the team,
not just the person who built the setup. Here’s what it unlocks, per product.
I have been working pleasantly with i-spark for quite some time. The combination of thinking along and practical application unburdens me and is exactly what I am looking for in a partner.
Sdu
The expertise of i-spark is a working and welcome addition to that of our teams at ID&T.
ID&T
Thanks to i-spark’s expertise, our data is no longer a by-product; it’s a growth engine. We now enrich our internal systems, optimise operations, and inform customs authorities with ease.
WWL