Vertical software house
You have a niche — clinics, fintech, logistics — and want to build a dedicated ERP for that niche, sold to your existing client portfolio. The vertical blueprint becomes your asset.
ProjetoBUILD PACT
RevisãoREV. 01
Data2026
EscalaB2B
Build partnership
Build your client's vertical ERP with two devs and Forge.
Reuse blueprints across projects, maintain margin, deliver with enterprise governance already built in.
Identification block
- Partner
- Software house, integrator, or consultancy
- Aether
- Platform + Forge + regulatory compliance
- Scope
- Vertical construction on shared base
- Entry
- By commercial and technical qualification
Section 01 — The dilemma
Three paths. The third is not obvious.
Every vertical software house owner knows the dilemma. There is a third path — and it is neither of the first two.
Caminho 01
Build from scratch
Enormous cost, endless maintenance, evolution slower than market demand.
Caminho 02
Resell a third-party ERP
Low margin, dependency on someone else's roadmap, diluted vertical identity.
Caminho 03
Build on the platform
Use another's platform while preserving your vertical identity, with real productivity amplification. That is the Aether + Forge path.
Section 02 — The model
What you gain by building with Aether and Forge
You build the vertical product for your client using Forge as a productivity amplifier and the Aether platform as the base.
- 01
Delivery speed
A small team with Forge tends to deliver in months what a team several times larger would take a year to deliver.
Conservative projection — to be validated with the first partners
- 02
Reuse across clients
A blueprint built for the first client is 60% to 70% reusable for the second in the same vertical — your ticket drops in time, not in price.
- 03
Built-in enterprise governance
What you deliver to the client already includes database-level data isolation, segregation of duties, and immutable audit. Capabilities that would cost man-years to build from scratch.
- 04
Preserved identity
You sell to your client under your brand and your relationship. Aether is the platform underneath — recognized where it makes sense, invisible where it does not.
- 05
Regulatory compliance ready
NF-e, NFC-e, CT-e, NFS-e, SPED, eSocial, Educacenso, and Agro-RX — already in homologation, without a third-party plugin.
Section 03 — Three partner types
Three profiles, three structures
Not a generic channel. A build partnership with a specific fit for each operation type.
Enterprise integrator
You customize ERP for large companies. With Forge, your deliveries accelerate — headquarters and multiple branches coexist with regional specialization, without duplication.
Technical consultancy
You are the partner that extends the client's team. Forge amplifies your engineers — the same team delivers more without hiring.
Section 04 — Licensing tiers
Three tiers sized to your operation
Forge has three tiers. What changes between them is the team structure and SLA — not access to the product.
Specific values for each tier are handled in a qualified conversation, not published on the site.
Tier
Team
Scope
SLA
Builder individual
One engineer
Unlimited projects
Standard
Team
Up to five engineers
Unlimited projects, collective throughput
Differentiated
Agency
No engineer limit
Unlimited projects, collective throughput
Dedicated, priority support
Section 05 — Partnership economics
The gain is not just time. It is the capacity to serve more clients in parallel.
Example with a mid-size project — vertical ERP for a client in your portfolio.
SCENARIO A
Without Forge
- Larger dedicated team, allocated over an extended cycle.
- High operational cost on the project.
- Tight delivery, little room to iterate with the client.
SCENARIO B
With Forge
- Smaller team, allocated over a shorter cycle.
- Reuse of the vertical blueprint across clients in the same niche.
- Delivery with built-in governance — less infrastructure to build afterward.
The structural gain is the ability to serve two or three clients in parallel with the same team that previously delivered one.
Model projection — specific numbers for your operation are handled in a qualified conversation.
Section 06 — Scope division
What stays with you. What stays with us.
The division is clear. This is not a model where everyone sells to everyone.
WITH YOU
Party A — Partner
- 01Commercial relationship with your client.
- 02Brand identity.
- 03Specific vertical value proposition.
- 04First-line support to the end client.
- 05Recurring revenue from the client.
WITH US
Party B — Aether
- 01Platform — closed core, continuous evolution.
- 02Forge — construction agent.
- 03Fundamental governance and native regulatory compliance.
- 04Partner support on platform matters.
Party A — PartnerAssinatura
Party B — AetherAssinatura
Section 07 — What is not an Aether partnership
Honesty about fit
Some partnership forms do not fit this model. We say so upfront, not after.
Commodity resale
A partner looking for low prices to resell without building is probably not the right fit.
White-label without control
The platform core remains ours. The partner builds on top — does not fork the product.
Extended free trial
The partnership requires investment on your side. Our expectation is reciprocal seriousness.
Purely technical
Partnership works when there is commercial and market alignment — not just tool alignment.
Section 08 — Next steps
How the partnership begins
Qualification
A 30 to 45-minute conversation about your market, portfolio, and team.
Scope alignment
Which vertical, which tier, which proof project.
Technical onboarding
Access to Forge, configuration, and first blueprint.
First client
Typically an existing client of yours, to build the base blueprint.
Build partnership pact
Controlled entry, reciprocal seriousness.
The partnership begins with a qualified conversation. Controlled entry by fit — not by volume.
END OF PACT