Stadsbeheer

Name: Stadsbeheer
Brand: Stadsbeheer

🟧🟦 Alles voor een optimaal omgevingswet, vergunningen-, toezicht- en handhavings-systeem. https://stadsbeheer.com/

Est 2003|15 Ref Customers

LinkedIn 961|Website|FTEs 25|HQ Zwolle, Overijssel, NL

MarketsBusiness Process Management (BPM)

Published Sep 11, 2026

01Common complaints

- Organization sizes or stages where this product is excessive or insufficient - Very small municipalities or organizations with minimal VTH complexity and limited IT capacity may find the implementation overhead disproportionate. - Industries or use cases where competitors are clearly more appropriate - If a procuring organization requires a broader municipal suite with standardized ecosystem integration across multiple municipal domains, a larger suite provider such as Centric may be a better strategic fit. - Technical requirements that this product cannot meet (based on public documentation) - If the procurement requires publicly published security attestations, formal trust-center documentation, specific uptime SLAs published publicly, or explicit data residency guarantees, current public documentation is insufficient to validate those requirements. - Budget constraints that make alternatives more appropriate - Organizations unable to fund professional services for integration and local process tailoring face a higher risk of cost escalation. - Specific workflows or integrations where the product has exhibited risk - Integration and data conversion have been identified as delivery risks in at least one municipality; highly customized landscapes or poor-quality source data may increase implementation friction. - Red flags in the buying process - If project timelines are driven by external regulatory go-lives (for example, Omgevingswet changes) and the rollout is accelerated, the Heusden case suggests a substantial risk of additional consulting spend and schedule slippage. - Current limitations acknowledged in public sources - No explicit public list of software defects was found on product pages. Public procurement documents note integration and conversion challenges during some projects. - Roadmap availability - No dated public product roadmap was found in the reviewed sources. - Scale limitations - Scale and performance limits are not publicly documented. - Security or compliance gaps - Publicly visible security certification evidence (SOC 2 / ISO 27001) was not found; such evidence may be available under NDA but cannot be assumed from public materials. - Technical debt or architectural limitations mentioned in reviews - No mainstream user reviews were found to detail technical debt or architectural limitations. - API limitations or integration constraints - Integrations and data conversion were identified as a significant delivery risk in at least one municipal implementation; specific API capabilities and constraints were not fully documented in the public materials reviewed.

Deal disqualifiers: what makes a poor fit

Organizations that require publicly available SOC 2 / ISO certification evidence prior to procurement (unless the vendor can provide these under NDA).
Organizations that require transparent self-serve pricing and rapid procurement without implementation services.
Organizations with very limited internal capacity for process design, data migration, and integration testing.

Why some customers left for competitors (churn reasons)

No explicit, independently verified statements of customers switching away from LEEF to specific competitors were found in accessible sources. Where vendor materials describe replacements, the context often involves legacy products that were end-of-support rather than a direct vendor-to-vendor comparison.

02Why they buy

- Reported competitive advantages (from customer statements and public documents) - Customer statements in vendor materials indicate relative ease of initial navigation, a reduction in unnecessary navigation steps, and perceived continuity support during staff turnover through structured implementation plans. These are qualitative observations reported by customers. - Unique features and capabilities not independently verified - Independent sources did not conclusively demonstrate features unique to LEEF beyond its emphasis on tailoring workflows to municipal processes. The primary differentiator in available materials is the vendor’s service-led implementation model and configurable workflow focus. - Areas where competitors have advantages (balanced view) - Larger competitors may provide more complete compliance documentation, standardized procurement packs, and broader product suites that address multiple municipal domains beyond VTH.

Why customers chose this product over alternatives (inferred)

Drivers evidenced in public-sector materials include:
- Need for a VTH system compatible with Omgevingswet/DSO integration timelines.
- Replacement pressure when legacy systems were no longer supported.
- Preference for configurable workflows and vendor involvement in process design.

03Field reports

Availability of mainstream review-platform coverage (Gartner, G2, TrustRadius)

No product listings or reviews for Stadsbeheer/LEEF were found on major public review platforms during this research. LEEF appears to be a regional/niche public-sector product with feedback primarily surfaced via vendor materials, government procurement documents, and academic work.

Vendor-published testimonials (summary)

Vendor-published materials include customer statements indicating increased insight into running cases, perceived efficiency improvements in communication, and reduced navigation errors following implementation. These statements are vendor-provided and generally qualitative.

Critical/negative evidence (implementation pain, cost overruns, system-chain issues)

A municipal procurement/implementation document describes implementation challenges, need for additional external expertise, delays due to integrations and conversion, and costs that exceeded initial estimates.
The same document highlights dependency risks related to national digital infrastructure (DSO performance) affecting case intake completeness.

Specific outcomes customers achieved (with metrics when available)

Reported customer outcomes are mostly qualitative (for example, improved insight and communication speed). Public municipal documents report vendor-published commercial terms (license, implementation, and support costs) but do not report standardized operational KPIs.

Vendor case studies/testimonials (marketing-led)

Stadsbeheer publishes customer stories that name municipalities and agencies. These materials demonstrate breadth of deployments but are qualitative and not independently verified.

Independent/public-sector case evidence (more critical)

- Heusden (college proposal) provides concrete implementation detail: - Purchased LEEF in 2021 to replace Squit XO. - Go-live target was July 1, 2023; actual go-live occurred on October 1, 2023 due to integration and conversion issues. - Confirmation of the Omgevingswet for Jan 1, 2024 required additional effort. - Costs documented: an initial documented investment covering multi-year licensing and implementation, plus additional documented support costs. - Additional repair work was required because DSO intake at the start of 2024 was not functioning optimally. - Critical evaluation: - This case suggests that LEEF implementations can require program-level coordination rather than a simple software rollout. Some problems originate upstream (DSO), but the operational burden still falls on the municipality, integrators, and vendor.

Academic evaluation (service quality lens)

A 2022 Radboud University master’s thesis titled “De kwaliteit van LEEF” evaluates service delivery quality in a municipal context and provides a structured assessment framework. The thesis focuses on the broader municipal service delivery concept around LEEF and is useful for organizational- and service-level analysis.

04Best fit

Organization types and sizes

Primary: municipal and regional public-sector bodies in the Netherlands, particularly those with dedicated VTH/physical environment teams.

Industries and verticals where adoption is strongest (with customer examples)

Local government: Dutch municipalities. Named municipal references in vendor materials include Voorne aan Zee, Hardenberg, Brummen, and FUMO.

Roles and personas: decision makers AND end users

Decision makers:
- CIO / IT manager within the municipality
- Domain managers for physical environment / VTH
- Procurement and compliance officers
End users:
- Permit officers (vergunningverleners)
- Inspectors / supervisors (toezichthouders)
- Enforcement officers (handhaving)
- Functional administrators / application managers

Pain points and challenges the product addresses

Managing complex VTH case workflows across departments and partner organizations
Deadline/term monitoring and work queue visibility
Balancing standardization with local tailoring under the Omgevingswet
Document and email generation and archiving into linked case/DMS systems

Qualification criteria: what makes a suitable fit

The procuring organization should have clear internal ownership for VTH process design and be prepared to engage in joint workshops with the vendor.
Integration resources (internal or partner) should be available for DSO, zaaksystem, DMS, and registries.
The organization should prefer a vendor-led implementation approach rather than purely self-service deployment.

05The pitch

What the product does (core value proposition in objective terms)

- Stadsbeheer B.V. develops and implements LEEF, a Dutch VTH (Vergunningverlening, Toezicht en Handhaving — permitting, supervision/inspection, and enforcement) application used by municipalities and related public‑sector bodies to manage cases from intake through permitting decisions, inspections, and enforcement workflows. - The product is positioned as configurable to align with each customer’s processes rather than a fixed standard system. Features include work queues, deadline/term monitoring, role‑based screens, document/email generation, reporting, and integrations to common Dutch government registries and case/document systems.

Target market and market positioning

- Primary: Dutch municipalities (gemeenten) and omgevingsdiensten (environmental services / regional enforcement agencies) managing regulated activities under Wabo and the Omgevingswet. - Secondary/adjacent: other public‑sector organizations referenced by Stadsbeheer as customers/targets (for example, safety regions are mentioned in recruiting materials). - Market posture: a VTH software product delivered with implementation and advisory services rather than a purely self‑serve SaaS model.

Get a comprehensive analysis of Stadsbeheer including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →