Product overview
The Pico ecosystem profile.
Download an overview covering product groups, business problems and contact details.
Documents & FAQ Clear information.
Clear information.
Focused discussions.
Overview documents and the questions to clarify before defining project scope.
Downloadable documents
-
-
Prepare for the discussionRollout scope checklist.
Business problems, users, data, integrations and operating requirements to prepare.
-
Product interfacesExplore by product.
Pick a software group to see illustrations and the related workflows.
View product interfaces
Downloads are interim versions generated from the website content. Official PDFs will be published once Pico finalizes them.
Perspectives Digitization starts
Digitization starts
with the business process.
Three points to agree on before choosing software.
-
Launch Digitizing a launch starts with distribution rules.
A launch event needs consistency between inventory, selection order and each party's permissions.
- Align product statuses and reservation rules.
- Define the order of booking, check-in and unit selection for each event.
- Clarify the rights of agencies and the developer, and how exceptions are handled before launch day.
-
Contracts & receivables Contracts and receivables need one shared transaction record.
Payment obligations must be tied to the terms, schedule and changes of each contract.
- Link customers, products, contracts and payment schedules.
- Record adjustments, extensions and approvals for traceability.
- Align data sources and reconciliation rules across sales, contracts and accounting.
-
Resident care Resident care needs a clear handling flow.
The resident experience is shaped by how requests are received, routed and answered.
- Create an easy intake point and classify requests.
- Define owners, statuses and handoff steps.
- Notify progress, confirm completion and capture feedback to improve service quality.
FAQ What businesses
What businesses
usually want to clarify.
Do we have to deploy the whole ecosystem?
There is no need to assume you will replace the entire system from day one. Share your priority problem and we will define the right product group and roadmap.
Can Pico connect to SAP?
Pico has confirmed SAP S/4HANA integration within Booking, CRMCRM: Customer, contract & receivables management, CPMSCPMS: Building operations management and Workflow. Data, master source, direction of exchange and sync schedule are defined per project.
Does Pico CRMCRM: Customer, contract & receivables management connect to or replace LandSoft?
Pico CRMCRM: Customer, contract & receivables management is positioned to replace LandSoft CRMCRM: Customer, contract & receivables management. Booking is not in the scope of the LandSoft integration. Migration, reconciliation and Residence/CMSCMS: Member, voucher, event & news management connections are defined separately based on your current setup.
Do Agency and Admin have the same permissions?
No. Agency can view customers, inventory and sales policies, carry out booking tasks and track commission within the scope granted. Creating accounts, assigning permissions and other administrative tasks belong to Admin.
Can customers view contracts in the app?
The customer Mobile App connects to CRMCRM: Customer, contract & receivables management and contract data, along with Booking, Residence, Event and relevant content. The interface and access scope are defined per deployment.
Is e-signature required?
No. CRMCRM: Customer, contract & receivables management generates contracts from templates and runs an approval flow. E-signature is integrated depending on the developer's needs and the agreed scope.
How long does deployment take?
There is no single timeline for every project. The number of modules, configuration requirements, data readiness, integrations and the number of deploying units must be defined before planning.
How is the cost determined?
We need to clarify modules, usage scale, configuration/customization, data, integrations and support scope. Commercial components are agreed in a separate proposal; the website does not apply an assumed price.
Where is the data stored?
The infrastructure option and storage location are confirmed within the project scope. The website does not assume a cloud or customer-server model before it has been agreed.
Are support or response time commitments offered?
Support channels, priority levels, intake hours and response times must be stated in the deployment agreement. Do not infer an SLA from mockups or product introduction content.
Are the screens on the website the real interface?
The interface images are mockups created separately to illustrate business processes. The data shown is fictitious; real screenshots will replace them once provided and approved by Pico.
Does an integration logo mean a certified partner?
No. Logos identify systems that can be connected, based on information provided by Pico. They are not a claim of certification or an official partnership with the vendor.
Let's design the right journey for your business.
Share your business model and current systems. The Pico team will work with you to define the right direction for the discussion.