AscendixRE is a managed commercial real estate CRM package that Ascendix Technologies builds on Salesforce. Adopting it well is an architecture decision, not a purchase: the licence topology, the CRE data model and the automation you inherit all set limits that are expensive to discover after go-live. Twopir Consulting settles those questions first. Fit, licence and data model — decided before anyone builds.
Trusted by 500+ organizations — and built on the Salesforce ecosystem platforms that commercial real estate teams actually run on.
Built for Commercial Real Estate
AscendixRE is a capable package. Almost every troubled rollout we are called into failed on a decision made before the build started — not on the software. These are the six we see most.
Ascendix bundles an OEM Salesforce licence in every AscendixRE tier, but also deploys into orgs clients already own. The two topologies behave differently, and nobody asks which one applies until a build decision depends on it.
AscendixRE keeps Salesforce's party and activity spine and replaces its sales spine. Teams expecting Lead and Opportunity find Inquiry and Deal, discover that a Property is the building and that Lease and Sale are the comp objects, and re-plan mid-build.
Closing a Deal writes downstream records — a leasing deal creates a lease comp, an investment sale creates a sale comp, the related Availability can be closed out. Redesign Deal stages without mapping that logic first and the comp history quietly stops being created.
Ascendix's Property import processes in 99-record chunks, and one bad record blocks that chunk's address updates. Plans built around a single clean load meet reality on the first attempt and the timeline slips before anything else has started.
Ascendix states plainly that it does not promote or partner with third-party apps. There is no vendor-supplied connector for the market-data, e-signature or accounting tools most brokerages assume are included — each one is real scope.
Commission privacy and who can see whose pipeline are first-class requirements in a brokerage, not switches. Sharing model, permission sets and commission visibility have to be designed with the data model — retrofitting them means reworking it.
AscendixRE is a managed Salesforce package, published by Ascendix Technologies, that turns Salesforce into a commercial real estate CRM. It adds the CRE objects a brokerage works in every day — Property, Availability, Listing, Lease, Sale, Inquiry and Deal — along with commission tracking, rent schedules, stacking plans and CRE reporting. It installs from the Salesforce AppExchange as an auto-upgrading managed package, and it is sold in tiers: a foundations tier, an enterprise tier that adds Ascendix Search, Composer and commission tracking, and an AI add-on licensed per org rather than per user.
The architecturally important part is what it replaces. AscendixRE keeps Salesforce's party and activity spine — Account as the company, Contact as the person, Task and Event, Files, Chatter, Reports and Dashboards — and substitutes its own sales spine. Lead becomes the custom Inquiry object, with its own web-to-inquiry form generator and conversion dialog. The pipeline runs on Deal, segmented by business line for tenant rep, landlord rep, buyer rep, seller rep and capital markets. A Property is the building itself; Availability is vacant space within it; Lease and Sale are simultaneously the transaction record and the comp store. There is no separate comp object because there does not need to be one.
Who it fits. Brokerages, landlord and tenant rep teams, capital markets and debt advisory groups, and owner-operators who need property, availability, comp and deal data in one governed model — and who need commission visibility controlled by role. It is a poorer fit where the business runs on residential transactions, where Salesforce Essentials or Group editions are in play (Ascendix does not support them), or where the operating requirement is property management accounting rather than deal pursuit. Those are conversations worth having before a licence is signed, and they are the conversations we have.
What Twopir does, and does not do. We do not publish AscendixRE and we are not reselling it — Ascendix builds and licenses the package. We implement it: we assess fit, design the data model and sharing architecture around it, configure it against your deal flow, build what configuration cannot reach, integrate it with the rest of your stack, and support it afterwards. For the product's own reference material, Ascendix maintains a public AscendixRE help centre and an AppExchange listing.
These are three services with three different buyers, three different risk profiles and three different price points. Most confusion in AscendixRE scoping comes from treating them as one.
Getting AscendixRE live on clean data with the model, sharing and automation designed around how your business actually transacts.
Where it stops At a working system on your data. New objects and code are a separate decision, taken once the packaged behaviour is understood.
Everything the package exposes as configuration: field-level behaviour, layouts, mappings, permissions and the reporting layer on top.
Where it stops At the package's published limits — commission field sets cap at 10 fields, grids at 1,000 records. Past those, it is a build.
Custom development around AscendixRE where the business requirement genuinely exceeds what the managed package was designed to do.
Where it stops At the managed package boundary. We never modify Ascendix's components — we build alongside them, so their upgrades keep working.
AscendixRE ships as a managed package with automatic upgrades, so its objects, fields and logic are not yours to edit. Everything we build sits beside the package and references it, never inside it. That is what keeps an Ascendix release from breaking your customisations — and it is the single most common reason a heavily customised AscendixRE org becomes expensive to maintain.
A consulting engagement produces a written architecture and a scoped plan — not a demo. Each of these is a deliverable you keep, whether or not we build it.
Whether AscendixRE is the right answer for your business lines at all — and what the honest alternative looks like if it is not.
How Property, Availability, Listing, Lease, Sale, Inquiry and Deal will carry your portfolio, your pipeline and your comp history.
The licence topology, its downstream consequences, and the sharing model that makes commission data safe to keep in one system.
House splits, broker splits and thresholds mapped against what the package can calculate natively — and what will need building.
What you are actually migrating, in what order, and how clean it has to be before the first load rather than after the first failure.
A phased plan with the licence, integration and development costs separated, so leadership can approve a sequence rather than a lump sum.
Ascendix includes an OEM Salesforce licence in every AscendixRE tier, and also deploys the package into Salesforce orgs clients already own. Both topologies exist in the field, and almost every downstream constraint follows from which one you have.
| What it affects | AscendixRE on its bundled OEM licence | AscendixRE in your own Salesforce org |
|---|---|---|
| Salesforce licence | Included — Ascendix states no separate Salesforce licence purchase is required. | You already hold it, and you keep paying for it alongside the AscendixRE subscription. |
| Standard sales objects | Lead, Opportunity, Campaign, Quote and Forecasting are typically unavailable on an OEM licence — the likeliest reason the package ships its own Inquiry object. | All standard objects remain available, so AscendixRE's Inquiry and Deal sit alongside Lead and Opportunity rather than replacing them. |
| Custom object ceiling | Capped at 15 on the Enterprise tier — an entitlement ceiling that has to be budgeted across every future project. | Governed by your own Salesforce edition's limits, which are usually far higher. |
| Third-party AppExchange apps | Constrained. Installing other managed packages is not a given, which narrows the integration options available to you. | Unconstrained by the AscendixRE licence — normal AppExchange access applies. |
| Existing Salesforce investment | Runs separately from any Salesforce you already use, so a second system of record has to be reconciled. | AscendixRE joins the org you have, alongside existing automation, integrations and reporting. |
| Exit and data access | Read the data-exit terms closely — on an OEM licence, org access after termination is a genuine commercial risk. | The org is yours. Removing the package does not remove your Salesforce access. |
Ascendix publishes a user-facing help centre rather than a schema reference, so several things a solution design depends on — the package namespace, whether Deal is a custom object or standard Opportunity, and whether each relationship is a lookup or master-detail — are not documented publicly. We close them the only way they can be closed: a describe against a trial or sandbox org in the first week, before any design commits to an answer. Guessing here is how a data model gets rebuilt in month three.
A consulting engagement is typically two to five weeks depending on how many business lines are in scope. It ends with documents, not a deployment — and those documents are yours whether we build or not.
We map how each desk transacts — tenant rep, landlord rep, capital markets, asset services — and where property, comp and commission data lives today.
A technical inspection of the trial or sandbox org: namespace, object and field API names, relationship types, record types and what the packaged automation actually does.
The data model, sharing design and licence topology written down, with the gap between your requirements and the package's published limits stated explicitly.
Every requirement sorted into configure, build, integrate or defer — with the package constraint that drives each call recorded next to it.
A phased delivery plan with costs separated by licence, configuration, development and integration — ready to approve, and usable by any partner you choose.
The engagements below ran on Salesforce and Propertybase rather than AscendixRE. We show them because the hard parts are the same ones — property and listing data models, commission tracking, compliance workflow and integration discipline under a real brokerage's operating pressure.
Twopir Consulting transformed our real estate operations by unifying AML/KYC, inquiries, contracts, and commission tracking into a single Salesforce–Propertybase platform. Their API-driven approach automated workflows, reduced errors, and enabled real-time data synchronization. With improved visibility, collaboration, and compliance, we now operate faster, smarter, and with greater confidence.
Streamlining property management operations with Propertybase CRM automation.
Before we recommend AscendixRE to a brokerage, we read the package the way we would read any system we are going to be accountable for — the object model, the close automation, the published limits and the licence terms. That reading is the deliverable. It is also why our scoping conversations tend to be shorter than the rework they replace.
Luxury brokerages, proptech platforms and multi-state realty groups on Salesforce.
We help growing and mid-market companies solve complex CRM, integration, and business system challenges — and we work with enterprise organizations on the same terms. Commercial real estate is one of the practices where that discipline shows up fastest.
A fit assessment that can only conclude "yes" is a sales call. If your business lines are better served by a Sales Cloud build or a different CRE package, that is what the document will say.
Ascendix builds and licenses AscendixRE. We architect, configure, extend and integrate it. Keeping that line clear is how you know what you are buying from whom — and what happens to it at renewal.
Commission field sets cap at 10 fields. Editable grids display 1,000 records and update 500. Property imports run in 99-record chunks. We treat these as design inputs from day one rather than as surprises.
AscendixRE is a managed package on a platform we have worked in for over a decade. Sharing models, permission sets, Apex boundaries and integration patterns are the same discipline they always were.
The same team that writes the architecture implements, customises, integrates and supports it. Nothing is handed to a delivery group that was not in the room when the decisions were made.
Both are viable and the answer depends on how much of your business is genuinely CRE-shaped. AscendixRE gives you a ready CRE data model — Property, Availability, Listing, Lease, Sale, Inquiry, Deal — plus commission tracking, rent tables and stacking plans, so you are configuring rather than designing from scratch. A Sales Cloud build gives you complete control and no package constraints, but you are paying to design and maintain the CRE model yourself. The deciding factors are usually how standard your transaction types are, how much you need commission automation, and whether the 15 custom object ceiling on the packaged Enterprise tier is a problem for your roadmap.
Both models exist, which is exactly why this has to be settled first. Ascendix includes an OEM Salesforce licence in its AscendixRE tiers and states that no separate Salesforce licence purchase is required. It also deploys the package into Salesforce orgs that clients already own. The difference is not commercial trivia: on an embedded OEM licence you should expect standard Lead, Opportunity, Campaign, Quote and Forecasting to be unavailable, custom objects capped at 15 on the Enterprise tier, and third-party AppExchange installs constrained. In your own org, none of those limits apply. Confirm which topology is on the table before you scope anything.
Ascendix and independent reviewers describe two to four weeks for small teams, with longer timelines once customisation is involved. In our experience that range holds for a single business line on clean data with little integration. What extends it is almost always the same three things: data quality on the Property and comp history you are migrating, the number of business lines with genuinely different deal shapes, and every integration — because the package ships no vendor-supported third-party connectors. A consulting engagement exists to tell you which of those apply to you before a date is committed.
Configuration covers a genuinely wide surface: tab and field labels, record layouts and list views, field visibility, org-wide sharing and permission sets, Lightning record pages, the Object Field Mapping that drives deal close behaviour, and field-value logic through Custom Metadata Records. Development starts where the package's published limits bite — a commission dialog field set cannot exceed 10 fields or contain parent relationship fields, editable grids display 1,000 records and update 500 at a time, scorecards support neither attachments nor multi-currency. It also starts wherever an integration is required, since none ship with the package. Everything we build sits alongside the managed package rather than inside it, so Ascendix's automatic upgrades keep working.
No, and Ascendix says so directly: its help centre states that it does not promote or partner with any other third-party app, and redirects the question to whether the other vendor integrates with Salesforce. The documented exceptions are narrow — email parsing from LoopNet and Crexi that creates Inquiry records, an Outlook connection, and a Box integration article. Everything else is custom scope, and on an OEM-licensed org the option of solving it with a third-party AppExchange package may itself be constrained. This belongs in the business case, not in month six. Our AscendixRE integration services cover this work specifically.
Yes, and it is a design decision rather than a setting. AscendixRE is permission-set based, Ascendix documents configuring a user profile to see only records assigned to them, and commission privacy has been role-based since release 1.36 with sharing logic that covers broker collaboration during ownership changes. What makes this work in practice is deciding the org-wide default — usually private — alongside the data model rather than after it, because changing the sharing model later means revisiting record ownership, report visibility and every integration that reads those records.
Yes, and it is where a good share of our CRE work starts. An org can be live and still be operationally weak — comp history that stopped being created when someone redesigned Deal stages, commission calculations people no longer trust, brokers working in spreadsheets because the grids are slower than their habits. We assess the data model, sharing, packaged automation and adoption, then rebuild the parts holding the business back. That is usually a remediation roadmap rather than a fresh implementation, and it is covered by our AscendixRE support and managed services.
A fit assessment takes weeks, not months, and ends with documents you own — the data model, the constraint register and a costed roadmap. Whether we build it is a separate conversation.
Already decided? See AscendixRE implementation, customization, integration and support — or the wider Salesforce for commercial real estate practice.
