Obra Core
Paul · Product specialist · 34 s
Manage your property list, contacts, documents and access rights in one place. Other workspaces use the same data, so you do not have to enter it again.
For owners, managers and teams that want to move from separate records to one clear structure.
Obra CoreLess duplicate data entry and less searching across separate files.
Design of the product explanation · not a live product demo. Features and package coverage must be confirmed before publication.
Meet Paul
Obra Core connects your buildings, documents, tasks and partners. Every workspace builds on the same building passport.
Explore a practical example
Obra Core
Product specialist
Calls and live chat are not available yet. Contact us for more information.
Contact usPaul · Product specialist · 34 s
ObraPad brings property management together in an online platform, with a mobile app for iOS and Android being prepared for the pilot.
Bring building information and documents together, follow up tasks and maintenance, and work with your team and partners from the same record.
The app is being developed for work on site: open a building or installation via QR, record inspections and add evidence photos to the right record.
The mobile apps are being prepared for the pilot. Ask about current testing options and access.
Ask about the app and pilot accessOne building passport for office and field work, keeping information connected to the right building.
ObraPad is designed to keep Obra Core as the shared foundation while you add capabilities over time.
Building-specific activation and restricted installer access are being prepared for the pilot and verified end to end. Ask which scopes can currently be tested.
The pilot direction is to begin with one workspace and add more later.
The planned flow activates Construction only for the building being renovated; other buildings stay unchanged.
The access model is being developed so an installer or partner can use only the selected building, installation or task.
In the intended scenario, the installer only accesses the heat pump, its documents and assigned maintenance tasks in one building. Other buildings, financial information and private documents remain outside the scope. View, change, duration and revocation controls must be proven server-side before availability.
The design keeps an additional workspace and partner access as separate choices, with the building passport as the shared foundation.
Today: Addresses, contact details and plans are scattered.
Your workflow: Create the property, add its spaces and link the first documents.
The result: The other workspaces can refer to the same property.
Today: Each colleague maintains a separate list.
Your workflow: Record responsibilities and access on the shared record.
The result: Less uncertainty about who may use which information.
Today: A change risks turning into a new record.
Your workflow: Adjust roles and share only the relevant information.
The result: The building history is preserved; access remains limited.
The architect writes in Dutch. The contractor reads in Spanish. The reply and original stay with the same task.
Depends on configurationBring rental income, costs and documents together. Share only what you authorise.
Accountancy roadmapYou: Record which buildings, units and spaces belong to your organisation.
ObraPad helps: Other workspaces refer to that same property structure.
You: Link owners, colleagues, suppliers and other stakeholders to the correct record.
ObraPad helps: Access follows the configured role and property scope.
You: Store a plan, contract or photo with the property, space or installation.
ObraPad helps: The same document can be opened from a connected workflow.
You: Work with assignees, dates and outstanding tasks.
ObraPad helps: Views and configured reminders follow the task data.
You: Set a preferred language and discuss tasks or records with people who speak another language.
ObraPad helps: Translation keeps the original, source version, numbers, units and object references recognizable. Available languages and features depend on the configuration.
You: Review previous activities and share the relevant record with authorised stakeholders.
ObraPad helps: New activities build on the same history.
You: Gather your property list, contacts and documents. At the start, check what can be carried over and what still needs to be added.
ObraPad helps: A guided setup identifies missing fields and possible duplicate records; imports depend on supported sources.
You: Choose which organisation, people and roles may view or edit a property or assignment.
ObraPad helps: The link to the same property identity is retained when you switch workspaces.
You: Let the client explicitly decide which accountant may view and export which data categories.
ObraPad helps: The roadmap includes auditable exports and, later, read-only API/accounting connectors. Accountancy partner status does not automatically grant access to financial data.
Reuse the same property, contact and document data.
Search for or summarise information using the selected Copilot capabilities.
Determine who gets access and which data may be shared.
You define your workflow and boundaries. Routine can follow those rules; AI helps with preparation; exceptions remain visible. The capabilities you use depend on the available features and your plan.
Collect addresses, contacts and documents again for a new project.
Select the existing property and continue with the correct access rights.
Formula: number of tasks × (minutes now − minutes after the change) ÷ 60.
20 tasks × (15 − 10 minutes) = 100 minutes, or 1 hour and 40 minutes per month.
This is fictitious input, not a predicted product saving. Include checks and any additional actions. A negative result means additional time.
The editable calculation is available when this presentation is opened with JavaScript. Time freed up does not automatically represent a realised cost saving.
Property entities · contacts · documents · access rights. You continue with the same property context; you do not create a second record.
Core remains the shared foundation. Extensions add capabilities within the same data and rights.
An add-on already included in your plan is not offered again. The exact features, limits and any additional price are shown with your configuration.
Workspaces and add-ons explained →No. Start with the work you want to organise. The shared property foundation means you do not have to start over when you add an extension. Which components are included depends on the configuration.
That is not the intention. The intended access follows the assigned organisation, records, objects and roles, not merely the fact that someone has been invited.