Engagements and pricing
Advisory, product design and development are priced around the mandate, uncertainty and capacity. You receive a written proposal covering scope, deliverables and price before work begins.
Support with product choices, technical direction or capacity in your team. We work within an agreed mandate and contribute where you need us most.
You get: A prioritised recommendation, visible risks and a plan for the next step. Ongoing support has agreed capacity and responsibilities.
Discuss your needs ↗Make an idea or workflow tangible. We explore user needs, create prototypes and assess where AI could be useful.
You get: A prototype tried with relevant users, prioritised needs and a focused proposal for what to build first.
Discuss your product idea ↗We build software, integrations and AI features on commission. An AI product engagement starts with a concrete workflow. We agree on scope, quality and handover together.
You get: Testable releases, documentation and an agreed code handover. Operation and further development are scoped as part of the engagement.
Describe your product brief ↗Choose the starting point that fits your need. Scope, deliverables, responsibilities and price are agreed in writing before work begins.
For a clearly bounded discovery or delivery. The proposal specifies inclusions, acceptance criteria and how changes are priced.
For ongoing collaboration or work with substantial uncertainty. Agree rates, capacity and a budget limit, with approval before expanding it.
For deciding further investment after each delivery. Each stage has its own scope, cost estimate and decision point.
The specific proposal states the selected model, any VAT, third-party costs and payment schedule. Sending an enquiry does not place an order.
AI product engagements sit within commissioned product development. Evaluation, data foundations and human control are agreed explicitly. Product pilots have separate agreements, not general subscriptions.
Controlled professional pilot · access by arrangement
A workspace for the professional preparation of building projects. Brings together property information, drawings and documentation for professional review.
Scope, case type and access are agreed before a pilot. Municipal authorities and responsible professionals retain their roles.
Explore ProsjektKlar ↗
Pilot on request · scope and access to be agreed
Building and property facts through an API. We assess coverage, sources and refresh requirements for the specific use case before a pilot.
Price and integration are agreed after the data, source terms and intended use have been assessed.
Explore Datakilde ↗Send a few lines about the problem, who it affects and what you want to achieve. You do not need a finished requirements specification.
Describe your need ↗