In Wilkes-Barre, Pennsylvania, three people at one of the state's most established downtown organizations run property tracking, board reporting, tenant analysis, and stakeholder communications on a platform shaped specifically around their bandwidth.
Schedule a Demo
Since 2024, Diamond City Partnership has partnered with District360 as their technology partner to move off a previous CRM that never delivered the basics, and to build a place management system shaped around the bandwidth of a three-person team.
Property and tenant tracking with parcel-level block numbers, an Outlook plug-in for logging contact interactions, a one-click button to email the current board, custom dashboards for tenant occupancy and businesses opened versus closed, and a contact-account model that handles owners with multiple holdings.
Three people manage thousands of property, tenant, and stakeholder records on one platform. Board emails go out in a click. Tenant counts reflect who is actually active inside the district, parcel by parcel. The basics work, every day.
Diamond City Partnership is the place management organization for Wilkes-Barre, Pennsylvania, a city built on the diamond pattern of streets that gave it its name. The Partnership's three-person team of place managers is responsible for property data, business retention, member communications, board reporting, sponsorships, events, and the day-to-day relationships with property owners and stakeholders that hold a downtown together.
Before District360, that work ran on a previous CRM with functionality shortcomings the team had stopped expecting to be fixed. Contact logs were not user-friendly. Tenant data lived in spreadsheets updated parcel by parcel by hand. An event management module had been promised and had never materialized. Board updates went out one email at a time. The system was technically there, and almost none of it was being used.
For a team of three running a downtown, the cost was not just the software. It was the trust the team had lost in any tool that promised to make the work easier. Every new feature landed as a question of whether it would hold up once real work started flowing through it, and most of them did not.
District360 worked with the Diamond City Partnership team as a technology partner that would not over-build. A three-person team doing the work of a much larger downtown organization would not have been served by a wide rollout. The platform was instead set up around the way each role already worked, one capability at a time, with everything else deferred until the basics were genuinely in use.
The first move was to make District360 the single source of truth for the district, replacing the spreadsheet-by-parcel updates the team had been doing by hand. Properties got a block number field tied to the Partnership's own assessment database. Tenants moved into a structured audit so the team finally had an accurate, defensible count of who was active inside the district. The contact and account model was extended to handle the realities of downtown property ownership, where a single person often sits across multiple holdings.
The roadmap ahead is intentionally narrow. An event management module built directly from the team's actual planning workflow, rather than from a generic template. A list of small property-level field additions compiled from a year of using the system. The plan is to keep adding capability only as fast as the team can absorb it.
If your organization operates lean and your last CRM kept asking for more than you could give it, we would like to show you what a different kind of technology partnership looks like.
Start a conversationA typical week at Diamond City Partnership looks different from the way it used to. Property and stakeholder management runs directly inside the platform, with reports the team can pull without waiting on anyone. Property and contact records reflect what the team actually knows now, because every update lands in one shared system rather than a file someone else might not have seen. The event planning workflow is shaped around the way the team actually plans, rather than fitted to a generic data sheet.
Board updates that used to go out one email at a time now reach everyone in a single click. When the board asks how many tenants are active in the district, the number holds up, because every tenant gets counted once rather than once for each person listed on a lease. Occupancy and year-over-year changes in which businesses have opened or closed come back as charts the team can pull in seconds, not spreadsheets they rebuild every quarter. Email interactions with property owners go into the record only when the team chooses to add them. And when a specific question comes in, about a particular block, an industry, or a single property owner, the answer is already in the system rather than waiting to be reassembled.
The win here is not a long feature list. It is a short one that every member of the team uses, every day. Each new capability is added only after the previous one is in steady use, which is how the system keeps getting stronger without getting heavier.
Yes. District360 is built to scale down as deliberately as it scales up. Engagements with lean teams are paced around real capacity, with the basics prioritized first, larger integrations deferred until there is bandwidth to absorb them, and monthly check-ins kept focused on a short list of what is actually in use. Place managers running small organizations often find that the platform grows with the team rather than ahead of it. Diamond City Partnership, a three-person team running an entire downtown, is one working example of this approach.
Yes. District360 is built to sit alongside the field operations tools a place is already using rather than force a replacement. Field data from Block by Block flows in through the Smart 2.0 integration, and a deeper Block by Block integration is in active development with pioneering customers across the broader District360 network. Place leaders who already trust a field vendor do not have to give that up to bring property, tenant, board, and reporting workflows onto one platform.
The work is done in the open. Each capability is scoped from the team's actual workflow, built in a working session with the people who will use it, and reviewed in monthly check-ins where commitments are tracked. When something does not land on time, it is on the agenda the next month. There is no module that never appears. The Outlook integration, the board email button, the tenant audit, and the dashboards shipped at Diamond City Partnership were each built this way.
Every District360 engagement is structured as a year-over-year partnership, with a dedicated project manager and product specialist, monthly check-ins, and a rolling thirty, sixty, and ninety-day plan that the team helps shape. The relationship is built to keep evolving as the work changes.