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
demo

See what it can handle, before you decide.

We start with a guided demo of a business application that already works: customers, orders, documents, approvals, an AI assistant. Then, if it makes sense, we analyse your case and bring you a concrete proposal.

Book the demo
the path

First you see it, then we analyse, then we propose.

We don't ask you to imagine the product, and we don't promise a project after half an hour. It starts with a guided demo to understand what the platform can manage; if there is interest, two assessment phases turn your case into specifications; on those specifications we build a proposal with scope, timing and cost.

how it works

From demo to proposal, in four phases.

Each phase ends with a concrete output and a decision that is yours: you can stop at any point without having invested more than needed.

  1. 01

    Guided demo

    About thirty minutes, remote. We show you the base application at work on the areas that matter to you and answer your questions. At the end you know what the platform can do and whether it is worth going further.

  2. 02

    Preliminary assessment

    One or two sessions with the people who know the processes. We map what you do today, with which tools, for how many users and under which constraints. The output is a framing note: feasibility, priorities and an indicative scope for the first project.

  3. 03

    Detailed assessment

    On the chosen scope we go into detail: real documents and forms, exceptions, integrations with existing systems, regulatory and security requirements. We use structured interviews and adaptive questionnaires. The output is the functional specification of the project.

  4. 04

    Concrete proposal

    We present what we will build, in which order, with which timing and cost, where it runs and who maintains it. It is based on the specifications, not on a rough guess: you can compare it, take it to approval and, if approved, start from a first release.

the demo

A real application, not a slide deck.

In the demo we use a ready-made base application, populated with realistic sample data. It is not built for you and it is not your process: its purpose is to show you, hands on the product, how wide the range of what the platform manages is and what working with it every day feels like. Your own case is analysed afterwards, with method, in the assessment phases.

in the demo application

What you will see working.

Eight areas you find in almost every company. During the demo we focus on the ones closest to your work.

Master data and customers
Companies, contacts, history

Customer and supplier records with contacts, relationships, notes and the full history of interactions in one place.
Catalogue and orders
Items, price lists, statuses

A product catalogue with variants and price lists, orders moving from draft to shipped with their status always visible.
Documents and cases
Attachments, versions, deadlines

Cases with their documents, versions and deadlines: who uploaded what, when, and what is missing to close.
Workflows and approvals
Steps, owners, notifications

Requests following a defined path, with approvals, reminders and a log of every step.
Roles and permissions
Who sees what

The same data shown differently to sales, accounting and management. We switch user and you see the difference.
AI assistant with confirmation
Requests in plain language

Ask the assistant for an operation in words: it shows you what it is about to do and waits for your confirmation before running it.
Search and dashboards
Filters, views, exports

Search across all data, saved views, summaries by status and period, Excel export when you need it.
Integrations and APIs
ERP, e-commerce, email

How the application talks to the systems you already have: every piece of data is available through documented APIs.

before booking

What you need, phase by phase.

For the demo you don't need to prepare anything. For the assessments, bringing real material — even informal — makes the difference.

Useful for the assessments

  • A concrete process that lives on Excel, email or paper today.
  • Real documents you use: forms, orders, sheets, reports.
  • The names you use internally for things and steps.
  • Which systems surround you and whether they expose interfaces.
  • The exceptions your current software handles poorly.
  • Who should use the solution and how much time they can give to the analysis.

Not needed

  • A tender or requirements document: we write it during the assessment.
  • Production data for the demo: the application uses sample data.
  • A decision already made on budget or scope.
  • Technical skills: demo and assessments work with non-technical people.
faq

Demo and assessment: the questions.

Is it a sales presentation?
No. There are no positioning slides: we show you a working application and use it in front of you. If at the end we tell you that an off-the-shelf vertical product suits you better, that is a possible outcome and we say so.
Is the demo built on our case?
No, and that is deliberate. We use a base application with sample data, the same for everyone, so you see the product for what it is. Your case deserves a proper analysis, which is the job of the preliminary and detailed assessments.
Who should attend on our side?
For the demo, whoever needs to understand whether the platform fits: often an operations manager and a decision maker. The assessments need the people who know the processes in detail and, for integrations, someone from IT.
Do we need to give you access to our data?
Not for the demo or the preliminary assessment. In the detailed assessment we work on sample documents, anonymised if you prefer, under a confidentiality agreement. Access to real systems and data only comes up in the project phase, with the appropriate agreements.
How long do the phases take?
The demo about thirty minutes. The preliminary assessment one or two sessions. The detailed assessment depends on the scope: a single process usually takes a few weeks, several departments take longer. Timing is agreed before starting.
What does the final proposal contain?
Functional scope, a phased release plan, timing, cost, the operating architecture (cloud, on-premise or hybrid) and who takes care of maintenance and evolution. It is written on the assessment specifications, so you can check it point by point.
How long from request to demo?
Usually a few business days. We write to you to set date and time as soon as we receive the request.
book

Book the guided demo.

We'll get in touch to set a date and time: about 30 minutes, remote. If it makes sense afterwards, we'll organise the assessment.