The partner holds the license. Almaneo does the build.
We deliver Fabric, Azure, and AI builds for the clients of Microsoft distributors and partners, under the partner's brand. The partner owns the client relationship and the contract. Almaneo joins as the technical execution of the partner's project.
We take on the build
From diagnosis to pipelines, dashboards, and agents, in code, fast, and reproducible. Build effort is quoted from measured figures, not gut feel.
We deliver in a state the partner can operate
We do not build black boxes that cannot run without Almaneo. Runbooks, scripts, and training are part of the delivery.
We can deliver under the partner's brand
What the client sees is the partner. Almaneo builds behind the scenes.
Division of roles
| Area | Owner |
|---|---|
| Client relationship, contract, sales | Partner |
| Licensing (CSP, F-SKU) | Partner |
| Build (diagnosis, design, pipelines, BI, agents) | Almaneo |
| Operations (after delivery) | Partner, with Almaneo providing handover training and stabilization support |
Standard build — 7 to 11 weeks plus 30 days of stabilization
| Stage | Duration | Work → Deliverable |
|---|---|---|
| ① Diagnosis | 1 week | tenant, capacity, licensing, and security checklist review → diagnosis report and recommended configuration |
| ② Design workshop | 1 to 2 weeks | business interviews → data model design document, scope and fixed price confirmed |
| ③ Build | 4 to 6 weeks | source ingestion, pipelines, 2 to 3 dashboards, automated reports/agents → everything deployed from code |
| ④ Operations handover | 1 to 2 weeks | runbooks plus the full set of automation scripts → training for the partner's operations staff |
| ⑤ Stabilization | 30 days | issue response and questions |
Delivery criterion — the partner can operate without Almaneo.
Note — we have measured a full workload run on the smallest capacity (F2). Pay-as-you-go operation is possible, turning on higher capacity only when needed.
Deals do not die
A project started wrong strains the partner's client relationship. We apply assessment criteria before starting, but a project that is not a fit is not rejected; the prescription changes within the channel.
| Situation | Prescription |
|---|---|
| Needs a transaction processing system (orders, production execution) | classified as a business system and referred accordingly |
| One source and a few reports | Power BI alone (also a partner channel product) |
| Already operating Databricks or Snowflake proficiently | coexistence design instead of full migration |
| Air-gapped or on-premises required | stated before starting that this is SaaS only |
The Microsoft ecosystem beyond Fabric
| Phase | Area | Detail |
|---|---|---|
| Now | Fabric builds | F-SKU plus consumption of adjacent Azure resources |
| Expansion 1 | Azure builds | new service builds and migration of AWS and GCP workloads to Azure — turning third-party cloud spend into partner CSP revenue |
| Expansion 2 | Azure AI services | internal search, document automation, and chatbots on Azure OpenAI and AI Search — lightweight projects that start without Fabric |
| Exploring | M365 and Power Platform integration | Teams and SharePoint integration, Power BI rollout to business users |
Expansions 1 and 2 are not declarations; they are already partly proven. Every Azure resource in the proof of concept was created through CLI automation, and our experience building and operating on other clouds means we know both ends of a migration.
Kickoff checklist — moving mid-project problems to before the contract
Half of where data platform projects get stuck is outside the code. We organize the knowledge that rarely appears in documentation and is only gained by measurement into six areas, and check them before the contract.
Item-level detail is provided after the partner agreement.
Start with a pilot project
We run the first build as a pilot project and use the result to confirm the standard build offering and terms.
Ask about the Partner Program