Question 1

Is Sentus secure enough for owner statements, bank details, and sensitive property documents?

Accepted Answer

That is exactly the standard buyers should hold us to. Sentus is built around company-scoped access, role-based visibility, challenge and rate-limit controls, secrets managed outside the codebase, and a public Trust Center with live control status and downloadable diligence artifacts. If that bar matters to your owners or investors, it should be part of the buying conversation early, not after implementation.

Question 2

Can owners, investors, and property managers see reports and maintenance history without chasing updates?

Accepted Answer

Yes. The point of the platform is to reduce uncertainty and manual reporting loops. Buyers evaluating the owner, investor, and management portals should expect live financial visibility, document access, and operational history without waiting on one-off email packets every time a question comes up.

Question 3

How long does implementation usually take?

Accepted Answer

It depends on portfolio size, current system complexity, and how much migration or workflow redesign is involved. Smaller implementations can move quickly. Larger portfolios usually need a staged plan across discovery, migration, pilot, and expansion so teams are not forced into a brittle cutover.

Question 4

Do we have to rip out AppFolio, Buildium, Yardi, or our current tools on day one?

Accepted Answer

Not necessarily. Many buyers want to know whether the platform can be phased in or migrated responsibly. Sentus should be evaluated as an operating system, but implementation can still be staged around your current PMS, reporting needs, and internal change tolerance.

Question 5

What should we look for if legal, security, or procurement needs to review the platform?

Accepted Answer

Start with four things: the Security page, the Trust Center, the subprocessor list, and the procurement pack. Those pages answer the first buyer questions around data handling, access controls, AI governance, vendor exposure, owner or investor diligence, and implementation readiness before a deeper review session. Open the procurement pack →

Question 6

If our company requires SOC 2 certification, should we still talk to you?

Accepted Answer

Yes. Tell us that requirement early. We do not claim active SOC 2 certification today, but we do publish SOC 2-aligned controls, documented procedures, and evidence-backed trust materials. If certification is a gating requirement for your buying process, we would rather know that up front and scope the path honestly.

Question 7

How do you keep AI from making risky housing or compliance decisions on its own?

Accepted Answer

The product should be evaluated as an AI-assisted operating platform, not as an unsupervised black box. Buyers should ask where human approval is required, how AI actions are logged, how Fair Housing and consent risks are monitored, and how audit trails are retained. Those are the right diligence questions, and we answer them publicly in the Trust Center. Review the Trust Center →

The questions serious buyers ask before they commit.

Direct answers to the buyer questions that matter.

Most enterprise reviews move faster when the diligence path is explicit.

Need a buyer-specific review?