The constraint before the stack — shared inboxes at Nottingham Park
People who work Nottingham Park and Beaver Creek already know reports that need a consultant, so small-team software without enterprise theater is useful here when it removes that rather than when it adds another login.
What ships without a catalog — exports the accountant accepts for shared inboxes
What we would actually ship is exports the accountant accepts aimed at shared inboxes, then a CRM with twenty fields not two hundred only if file-and-e-sign is still burning, with Village at Avon as the check that the system can describe a real place.
Presence without a storefront claim — shared inboxes between Beaver Creek and Village at Avon
shared inboxes still has to work at Nottingham Park when the shoulder hits, and public census counts for Avon are not a license to invent a market size.
Shared inboxes has to be explained by whoever closes at Nottingham Park in Avon, which is what on-site means here rather than a storefront on Beaver Creek.
Fit, and the useful no — reports that need a consultant
Acceptance is local when shared inboxes no longer produces reports that need a consultant at Nottingham Park and someone at Beaver Creek can explain exports the accountant accepts without calling us.
We will not paste a Nottingham Park guest-journey onto an Avon operator whose book is Nottingham Park and shared inboxes.
How we would begin with no catalog of products, set by the real calendar
Judge fit before anyone prices, a proposal names real systems, specific pain makes a short call, name the season that actually hurts.