Skip to content

Resources

FAQ

Every answer below is one this site can stand behind. The questions it cannot answer yet are listed at the end rather than answered vaguely.

What is amkit?

An AI-native real estate asset management platform: one place to model your assets, data and relationships, configure the processes that move them, and put intelligence and agents to work across both.

What does “AI-native” mean here?

That the intelligence works with the same assets, data, relationships and workflows your teams use every day, rather than sitting beside them. You ask questions of your own portfolio and get answers grounded in its context; the platform surfaces changes, exceptions, risks and opportunities across assets; and it generates summaries, analysis and reports from information already inside it.

Not AI added on top — intelligence built into the way the platform works.

What do the agents actually do?

Three things, in this order. They understand, working with the context of your assets, data, relationships and business rules. They execute, taking on repeatable tasks and multi-step workflows instead of your team moving work from one system to another by hand. And they are governed: every action stays within the permissions, approval rules and operational controls you define.

Can it be configured to how we already work?

That is the premise. The data model, the workflows and the enterprise controls are all configured — portfolios, assets and the relationships around them; stages, rules, actions and approvals; roles, permissions and governance. The configuration is the substrate everything else runs on.

What does it cover?

Six connected business modules: investment forecasting, rolling forecasts, budget management, risk management, portfolio management and deal structuring. Financial modelling, scenario analysis and data integration support those workflows.

What does a review produce?

Depending on the workflow, a review can bring together revised forecasts, budget variances, risk responses or portfolio priorities, with the assumptions, evidence and next actions attached. The monthly operating review on the home page illustrates this flow; it is an example, not a live product screen or a customer result. Specific fields and automated actions depend on configuration and available capabilities.

How do we start?

Check demo availability. Demo booking is not open yet.

Still to be supplied

These come up in every evaluation and none of them can be answered from what this site knows today:

  • Which asset classes are supported, named rather than implied.
  • Whether customer data is used to train any model, and what leaves your tenant.
  • Which model providers the intelligence and the agents run on, and where.
  • Whether there is a public API, and what the developer platform includes.
  • Which systems have ready-made integrations.
  • Pricing, and what a deployment involves — timeline, effort and what amkit does versus what your team does.
  • Availability commitments, support hours and the terms attached to them.