What do you want to do?
Rent out property, follow up maintenance or manage a construction project. Your workspace brings the work and its related information together.
Pricing & configuration
Start with what you need.
Grow at your pace.
Make an initial choice of scale and workspaces. This design shows the configuration, not confirmed subscription prices.
Which extra capabilities do you want?
For example, automatically extract data from documents or use Copilot with your voice. Choose only what is useful for your work.
Everything stays connected through Obra Core. Your package determines which workspaces and extensions are included.
See the difference with examples →2. Which workspaces are relevant?
Obra Core is the foundation in this sample configuration.
3. Which additional capabilities are relevant?See the difference with examples →
An add-on is an extension, not an additional workspace. First check what your package already includes.
AI & voice control
Workspace Copilot and Copilot Voice: additional support within your chosen work context. Exact access and usage limits depend on the package.
Automatically extract data from documents
Document AI / OCR: proposed data extracted from documents. Storing documents and processing them automatically are different functions.
Cameras or bank reconciliation
Specific extensions with a separate connection, access and applicable usage unit.
Pilot direction: start with one workspace and expand later.
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.
Intended starting point
The pilot direction is to begin with one workspace and add more later.
Planned per-building expansion
The planned flow activates Construction only for the building being renovated; other buildings stay unchanged.
Planned access model
The access model is being developed so an installer or partner can use only the selected building, installation or task.
Intended example: heat pump maintenance
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.
