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
contact

Write to us directly.

No ticket system between you and the team building Pwas — write to us and we reply in person.

Chat with us
how we reply

What to expect after writing.

Who answers and how quickly.

Someone from the team answers, usually within one working day. There's no first line collecting and routing the request: the organisation is small and this is one of the few things where being small is a clear advantage.

If the question is technical, the answer is technical. If the question is "does this make sense for us?", the answer includes the case where the answer is no.

What to write so the reply is useful.

No formal document is needed. What makes a first reply genuinely useful rather than generic is very little: which process weighs on you today, which systems surround it and what made you start looking for something different now.

With those three pieces we can tell you something specific in the first reply — including, where appropriate, that your problem is better solved another way.

What we don't do.

We don't send newsletters and we don't share your details with third parties: what you leave us is used to reply to you and nothing else.

We don't make unsolicited sales calls: if you write with a technical question, you get a technical answer, not an attempt to book a meeting.

We don't reply with a sight-unseen quote. A serious estimate requires understanding the scope, and that requires at least one conversation.

frequently asked

Contact: the questions.

Do you prefer email or the form?
Either: the form arrives in the same inbox. Direct email to [email protected] is easier if you want to attach something or prefer writing from your usual client.
Do you answer technical questions with no commercial intent?
Yes, and we're glad to. A question about how a pipeline works or how a permission is declared gets a technical answer, without it becoming an opportunity to pitch. If a project grows from it later, so much the better.
Which languages do you work in?
Italian and English, both as working languages rather than as a courtesy. The site is bilingual for the same reason.
How long before we get a cost estimate?
A sensible estimate requires a defined scope, so typically after the demo and a conversation about constraints. What we can say earlier is the order of magnitude and which variables move it most — usually the integrations with existing systems.
Do you do consulting without the product?
The work of formalising a domain has value regardless, and in some cases we do it as a standalone activity — for instance where an organisation needs processes written down before a tender or a technology choice. In those cases the result is yours even if you then take a different route.
write to us

Tell us what you need.

We reply within one business day — directly, without going through a ticket.

Prefer to start with a demo?

Book 30 guided minutes on an application that already works.

Request a demo