Services
What Almaneo sells is not software but a build methodology. Here we publish the four-step process, the criteria for work we decline, and a four-week entry offering.
The four-step process
1. Diagnosis
We measure pain, data, and access. We start not with "what data do you have" but with "what was last month's most painful loss". If it is not a fit, we stop here and recommend an alternative. Fit assessment and consultation are free.
2. Design workshop
We agree on architecture, scope, success criteria, and the points where a person approves. A kickoff checklist moves the problems that surface mid-project (tenant settings, capacity policy, licensing, permissions) into pre-contract checks. The fixed price is confirmed here.
3. Code-based build
We build in code, not portal clicks. Every script is safe to run again, and the whole environment can be rebuilt from scratch. An environment made by clicking exists only in its maker's head; an environment made in code is both documentation and a handover deliverable. We work in day-level sprints.
4. Handover and training
We hand over runbooks, automation scripts, the golden set, and training together. The goal is a system that runs without Almaneo. Documentation and training are always included in the quote. Operations support is contracted separately, only when needed.
Agent Pilot — 4 weeks
One workflow, one agent. Four weeks from free diagnosis to handover, fixed price.
- Free diagnosis — measure pain, data, and access. If it is not a fit, we recommend alternatives such as spreadsheet automation, RPA, or BI alone.
- Design — pick one workflow and agree on success criteria, data sources, and human approval points.
- Build, 4 weeks — numbers from a calculation engine, narrative from cited evidence, human approval gates as the default structure.
- Handover and training — runbooks, golden set, and training included. Expansion is a separate contract.
Where to start
Management reporting
query ERP P&L data in natural language and generate reports automatically (print manufacturer: 10,000 ERP rows, 9 report types)
Document intelligence
search inspection certificates, work logs, and claim PDFs and produce briefings with cited sources (34 organizations, 153 MB, 0 parsing failures)
Advisory and recommendation
agents verified through tool contracts and a golden set (education domain: 8 tools, 800 golden set cases)
Work we decline
A project started wrong is a burden for the client and for Almaneo. In the following cases we say so before the contract and recommend an alternative.
- Projects whose core is a real-time core operational (transactional) system — we classify these as business systems and refer accordingly.
- Projects where data volume and frequency do not justify the investment — we recommend spreadsheet automation, RPA, or BI alone.
- Organizations already proficient in another stack — we recommend a coexistence design instead of a full migration.
- Environments where cloud is not possible, such as air-gapped networks — we state this before starting.
Why we do not publish prices
Almaneo does not quote by headcount times months. Build time is measured in days, not months, and cost is set by the scope and difficulty of the project, not by staff assigned. Publishing the same rate card with a different basis would only create misunderstanding.
Instead, we do this.
- Fit assessment and diagnosis consultation are free.
- After scope is confirmed in the design workshop, we present a fixed price. 50% at start, 50% after acceptance.
- If scope changes, we run a reassessment instead of billing extras.
- Handover documentation and training are included in the quote by default.
What we publish instead of prices: measured figures, the full process, and the criteria for work we decline.