Pricing and engagement

Fixed scope to start. Four ways to carry on.

We quote a fixed price after one scoping call, against a written scope you keep whether or not you sign. Every engagement starts with the three-week Discovery Sprint, and the sprint is not invoiced if the thin slice is not running on your data by day 15.

Discovery sprint

Three weeks to an architecture, a costed roadmap and a working thin slice on your data.

Fixed scope
Not invoiced if the slice is not running by day 15
See the sprint
  • Systems, data and process audit
  • Architecture and security review
  • Asgharian Core deployed against one hall
  • Working prototype of the highest-value piece
  • Costed six-month roadmap
  • Go or no-go with no obligation

Run and evolve

We operate what we built under an SLA and keep improving it.

Retainer
Per site or per platform
Talk about SLAs
  • 24/7 monitoring and incident response
  • Named engineer who knows your site
  • Monthly improvement budget
  • Quarterly architecture and cost review
  • Upgrades tested on a replica first
  • Handover option at any time

Embedded programme team

Multi-campus programmes that need a long-running product team.

Annual
Programme-level terms
Talk to us
  • Product, engineering and data roles
  • On-site presence as needed
  • Programme-level roadmap and governance
  • Security, compliance and audit support
  • Knowledge transfer to your teams
  • Core licensing across all campuses
Why there are no numbers here

A price before a scope is a guess

Two 40 MW campuses can differ by a factor of five in integration work, depending on whether the EPMS speaks Modbus or a vendor API, whether commissioning lives in Procore or in spreadsheets, and how much of the power tree exists as data rather than a PDF.

So we do the cheap part first. One 30-minute call, then a written fixed-price scope within two working days. You keep the scope either way.

Book the call
What you get

Six things, all yours, whether or not you continue

Every deliverable is a file, a repository or a running system in your own environment. Nothing is a slide.

01

A working thin slice

The highest-value piece of the eventual system, deployed in your cloud or on site, running on live data from one hall. Not a demo environment.

02

Systems and data audit

Every source we found: BMS, EPMS, DCIM, CRM, schedule. What each holds, its quality, its access path, and what is missing.

03

Architecture and security review

Target architecture, OT network plan with outbound-only collectors, data residency, identity, and what your security team will ask.

04

Asgharian Core on one hall

Collectors and the historian deployed and licensed for evaluation, so release one of a build starts from data, not from zero.

05

Costed six-month roadmap

Releases in two-week increments, team shape, budget ranges, and the decisions each release unlocks. Includes buy recommendations where a product is the right answer.

06

A go or no-go readout

Our honest recommendation in one page, presented to your decision-maker on day 15. Including “do not build this” when that is the answer.

Week by week

Fifteen working days, three demos

DAYS 1–5

Discover

  • Kickoff on site with your sponsor, ops lead and IT/OT access approver
  • Systems inventory and data access secured, read-only
  • Shortlist the thin slice by value and feasibility, pick one
  • Security questionnaire started

Friday: audit draft and chosen slice

DAYS 6–10

Build

  • Collectors live on one hall, historian receiving data
  • Thin slice version one against real points and records
  • Architecture drafted from what the data actually looks like
  • Your engineers pair with ours if you want them to

Friday: slice demo on live data

DAYS 11–15

Prove

  • Slice hardened and used by two or three of your people
  • Roadmap costed, team shape agreed, buy-versus-build calls made
  • Security review closed with your team
  • Readout to the decision-maker

Day 15: readout, roadmap, go or no-go

DAY
15
The guarantee

If it is not running on your data by day 15, you do not pay

We take the risk that the proposal usually pushes onto you.

  • If the thin slice is not running on your live data by day 15, the sprint is not invoiced.
  • If you continue to a build squad, the sprint is credited in full.
  • If you stop, you keep everything: the code, the audit, the architecture and the roadmap.
Which model fits?

Tell us where you are. We will suggest a starting point.

Suggested starting point

Discovery sprint

Book a discovery call
Compare

What each model includes

ItemDiscovery sprintBuild squadRun and evolveEmbedded team
Duration3 weeksMonthly, typically 6 to 18 monthsOngoingAnnual
TeamLead, engineer, architectLead plus 2 or more engineersNamed engineer plus on-call rotaProduct, engineering, data
DeliverablePrototype, architecture, roadmapProduction release every 2 weeksSLA and improvementsProgramme roadmap
Commercial basisFixed scopeMonthlyRetainerAnnual
Asgharian Core licenceEvaluationIncludedIncludedIncluded, all campuses
Code and data ownershipYoursYoursYoursYours
Security reviewIncludedOngoingQuarterlyProgramme-level
On-site presenceKickoff and closeAs neededIncident-drivenRegular
Support responseBusiness hours24/7, 1 hour for critical24/7, agreed per programme
Notice period30 days30 days90 days
Is a sprint right for you?

Honest fit, both ways

A good fit when

  • You develop or operate 10 MW or more and the answers to capacity, schedule or commissioning questions live in spreadsheets.
  • Your BMS, EPMS, DCIM and CRM disagree, and someone reconciles them by hand every month.
  • You want to own the software and the data, in your own cloud or on site.
  • A three-week sprint on real data is a reasonable way to decide.

Probably not a fit when

  • You need a packaged DCIM or BMS with no integration work. Buy one; we will say so.
  • The site has no telemetry and no plan to add any.
  • You want a twelve-month build with the scope frozen on day one.
  • You need staff augmentation without a roadmap or an outcome.
FAQ

Questions people ask before signing

Why start with a sprint instead of a proposal?

Because a proposal is a guess and a prototype is evidence. Three weeks on your data tells both of us whether the idea works, what it will take, and whether we work well together. The sprint is credited if you continue.

How is an engagement priced?

Every engagement is scoped and quoted for your site after a short conversation about phase, systems and goals. Sprints are fixed scope; squads and retainers are monthly; programme teams are annual. Book a call and we will give you a fixed price for your site in two working days.

Can we bring our own engineers into the squad?

Yes, and we encourage it. Mixed squads are the fastest route to handover. We pair, review together and keep everything in your repositories from day one.

What happens to the platform if we stop working with you?

Asgharian Core is licensed to you for the deployment with source access. You keep running it, with or without us. There is no per-point or per-user metering to renegotiate.

Do you work fixed scope for builds?

For well-defined scopes after a sprint, yes. Most clients prefer a squad with a roadmap they control, because priorities change as the site progresses.

How do you handle security clearance and site access?

Engineers on your engagement are named, background-checked where required, and inducted on site. Remote work runs through your VPN or a bastion you control.

Get a scope, not a brochure

Tell us about the site and we will come back with a fixed-price scope in two working days.