Does this only work with PebblePad?
PebblePad is our flagship integration because that's where we've seen the most acute reporting gap, but Deighta is designed as a portfolio-and-engagement reporting layer, not a PebblePad tool. We also support live API connections to TargetConnect and Studiosity today, and Mahara, OneFile, and other systems are on the near-term roadmap. If you've got a system that exports structured files or has a decent API, there's a path for it.
How long does setup actually take?
Typically 4 to 6 weeks end-to-end, from signed Statement of Work to dashboards live with real users. Discovery and spec phases take 1 to 2 weeks, the build itself 2 to 4 weeks depending on workbook complexity, with a week for UAT and training. API-based integrations like TargetConnect and Studiosity are faster because we skip the transformation-mapping work.
What does the admin on our side need to do?
For API integrations, effectively nothing after initial setup: the connection runs automatically. For PebblePad, the designated admin runs a scheduled set of exports on an agreed cadence (typically weekly) and drops the files into your Deighta workspace. We provide a short video, a one-page SOP, and a structured folder template. Most admins find it faster than their current reporting process.
What if our workbooks or configurations change mid-year?
Small changes (added fields, renamed columns) are absorbed without contract changes, we just update the transformation profile. Major structural changes (new workbooks, fundamentally new logic) are handled as change requests with fixed-scope quotes. Nothing is ever "we'll figure out the cost later".
What data actually leaves our institution?
Only what your designated integrations send, and only what's covered in your scope agreement. For PebblePad, that's the CSV exports your admin chooses to upload. For API integrations (including any agreed student system connection), only the specific fields and records we've scoped together. We never pull data we haven't agreed to, every transfer is logged, and you can revoke access at any time.
Can we get row-level security so tutors only see their tutees?
Yes, and it's the default. Tutor accounts are scoped to their tutee list. Programme leads see their programme. Strategic leadership sees aggregated views. Row-level security is enforced at the database layer, not just the UI, so it's not bypassable.
Is it built on Power BI, or is it a custom product?
Both, depending on the view. We use Power BI embedded (app-owns-data) where it earns its place, and custom React dashboards where we need to go beyond what BI tools can do comfortably, particularly for the engagement recommendations and future qualitative-insight features. Clients see a single branded product; we make the architecture decisions behind the scenes.
How is this priced?
A one-time setup fee, scoped against your data sources and complexity, plus a monthly SaaS subscription that covers hosting, maintenance, minor iterations, and support. API-based integrations are typically cheaper than file-based ones because there's less bespoke transformation work. We share detailed pricing during the discovery call once we understand your specific scope.