See Pwas at work: 30 guided minutes on an application that already runs. Book the demo →
Featured product
Pwas-One

ERP, Shop, CRM and Document Manager on one declarative domain, with an AI agent operating across every module.

ERPShopCRMDoc ManagerAI Agent
Discover Pwas-One →
The platform
Pwas.Framework
The backend, interpreted
Pwas.Client
The result, rendered
Pwas.Orchestrator
Intent, planned and governed
Pwas.Microservice
Extend the platform with your own tools
Ecosystem tools
Pwas CLI
Full-stack deploys, one command
Assessmefy
AI-driven adaptive assessments
Dynamic Registry Builder
From document to configuration
Compare products Pwas in your industry Book a demo
Pwas-One
ERPShopCRMDoc ManagerAI Agent
Pwas.FrameworkPwas.ClientPwas.OrchestratorPwas.Microservice
Pwas CLIAssessmefyDynamic Registry Builder
Solutions Industries Documentation Partners Request a demo Get Started
Italiano English
pwas.it — powered by pooel.it
partners · become a partner

Build Pwas projects for your clients.

For system integrators and software houses: direct access to the Pooel team, technical support on projects, training on the platform's primitives.

Apply Back to Partners
how it works

From application to first project.

No tiered certification path: a short, concrete process.

  1. 01

    Application and first conversation

    You tell us which clients you serve, what you work on today and where your current model breaks. It's about finding whether there's a genuine fit: if there isn't, we say so rather than opening a path that leads nowhere.

  2. 02

    Training on the primitives

    Sessions with the team on how the declarative model works, how to describe a domain and which mistakes are typically made early on. It's the part that demands the biggest change of habit for anyone coming from traditional development.

  3. 03

    First project alongside us

    A real project for one of your clients, with us beside you on configuration choices and critical points. The aim isn't for us to do it: it's for you to do it while seeing how the reasoning works.

  4. 04

    Progressive autonomy

    From the second project you work alone, with direct access for questions. In practice full autonomy arrives around the third project; platform matters and the more complex integrations stay shared.

  5. 05

    Field feedback

    What you meet in projects comes back and weighs on development priorities. At this stage of the ecosystem that channel genuinely matters — it isn't a courtesy.

quick check

Is applying worth it?

Probably yes

  • You sell bespoke projects and maintaining your portfolio weighs on you.
  • You have clients with processes no vertical product covers well.
  • You have vertical domain expertise you could turn into reusable configurations.
  • Someone on your team has the time and appetite to genuinely learn a new model.
  • You want to work directly with the people building the platform, not a channel.
  • Your clients are asking for AI in their processes and you don't want to improvise.

Probably not

  • You're looking for a product to resell at margin with ready-made sales material.
  • Your model is based on licences for already-mature vertical products.
  • You can't set aside time for initial training and a first supported project.
  • You need a partner programme with tiers, a portal and a directory already running.
frequently asked

Applying: the questions.

Are there entry fees?
There's no programme entry fee. Commercial terms concern the project relationship — resale, client-held licence or collaboration — and are defined together depending on how you work. We discuss it openly in the first conversation, before you invest time in training.
How long does initial training take?
In the order of a few days for an experienced technical profile, spread over time rather than concentrated. The demanding part isn't technical but conceptual: moving from thinking in code to thinking in domain declaration. Anyone who doesn't make that shift uses the platform badly and notices by the second project.
Do we need a client ready to go?
It helps a lot, because a first supported project on a real case is worth more than any exercise. It isn't a condition, though: you can start from training and building a demonstration configuration in a sector you know well, which then becomes useful material for your own proposals.
What support will we have on projects?
Direct access to the team for technical questions, with no ticket system. On the first project support is active; on later ones it's on request. For platform matters and complex integrations, support remains available regardless of how long the relationship has run.
Can we specialise in one sector?
That's in fact the route that works best. A partner who knows a sector deeply builds reusable domain configurations — entities, processes, controls typical of that market — which become their own asset and greatly shorten later projects. The industry pages on this site give a sense of the level of detail involved.

Ready to build your first project?

Tell us about your profile and the clients you work with.

Apply