Mark Anthony F.

Inadequate training can leave staff working around software rather than with it, effectively creating a second system. The suggested first step is to calculate the monthly staff time spent on the current process before buying—not simply assume that spending more will solve the problem.

A municipality chooses the lowest bid, then spends the supposed savings on workarounds, staff time and a second implementation.

Read original

Data formats, vendor-specific configurations and retraining can make a municipality dependent on one provider. Mark Anthony F. treats clear answers as a useful sign of a good vendor and warns that vague answers deserve scrutiny.

The post uses Apple’s monitor stand as an analogy for how an ecosystem can make switching feel too costly, then lists three questions for software vendors: Can the municipality export its data in a standard format?

• What happens to the data if the vendor is acquired?
• Who handles implementation, and how long will it take?

Read original

The post makes a general case for agility, rather than documenting a named project or comparing measured implementation times.

A township of 8,000 is contrasted with a larger city facing an 18-month procurement process and layers of meetings and committees.

Read original

Mark Anthony F. promotes DTC’s Master Calendar to schedule and track recurring jobs, including billing runs that can be carried forward from year to year. The post also pitches the product.

A utility’s recurring billing runs, reporting requirements and permit renewals can slip when they live in spreadsheets, sticky notes or one person’s inbox.

Read original

Its practical emphasis is on providing an integrated online route for residents.

A post says residents’ expectations for local government online keep rising and presents a municipal website paired with a self-service portal as the baseline for a working digital presence.

Read original

It is the quickest introduction to how this creator talks about municipal software deals.

Mark opens with Apple's $1,000 monitor stand: a product people mocked, then bought anyway, because once you own the phone, laptop and apps, leaving the ecosystem costs more than the stand.

• They apply the same logic to municipal software.
• Data sits in a format only the vendor supports; only the vendor understands the billing setup; switching would mean retraining everyone.
• Mark calls that not a partnership but a hostage situation.
• They offer three questions to ask before signing: Can we export all our data in a standard format at any time?
• What happens to our data if you are acquired?
• How long does implementation take, and who does the work?
• Good vendors answer clearly and quickly; bad ones get vague.
• The post closes by asking municipalities what question they would add.

For brands planning a campaign

The closest match for a procurement and vendor-management brief.

• The three questions could anchor a co-produced checklist, short explainer or live Q&A.
• Its structure — vivid analogy, numbered questions and an audience question — is reusable.
• Treat the claims as commentary drawn from experience, not independently verified vendor behavior.

Read it before deciding how to frame a procurement-focused collaboration.

A contract goes to the lowest bidder.

• Two years later, the municipality has spent three times the savings on workarounds, staff hours and a second implementation.
• Mark traces the pattern to the automotive industry, where companies bought cheap parts to save up front, then spent five times the savings fixing what broke.
• The sequence: the RFP goes to the lowest bidder, the software ships, staff receive little training, and they invent workarounds that become the new process.
• The municipality ends up running two systems — the one it paid for and the one staff actually use.
• Mark's prescription is not to spend more, but to measure the current process's monthly staff-time cost before signing anything.
• They close by asking whether a municipality has ever bought a system that created more work than it saved.
• The argument is framed as personal experience, with no named clients or figures attached.

For brands planning a campaign

Offers a ready-made TCO framing for agency or vendor content, and the prompt to "calculate what your current process costs per month" could become an interactive worksheet. The posts draw on first-hand experience rather than a published study, so any reuse should present the claim as Mark's observation.

Big cities have big budgets, but small municipalities have something better: speed.

• A township of 8,000 can decide in January and implement by March, with no 18-month procurement process, 47 stakeholder meetings, three committees or task force.
• Mark reframes the usual limitation — "we don't have IT staff" — as an advantage: no permission needed from an IT department, no integration with 47 legacy systems, no consultant to write the RFP.
• What matters is a solution that works and the authority to implement it.
• They end by asking what decision the reader's organization is fast at making.
• The claim is general; no specific communities or projects are named.

For brands planning a campaign

Offers a size-based audience angle that positions smaller municipalities as leading rather than lagging — useful for content aimed at smaller buyers.

• The closing question is a ready-made engagement prompt.
• The speed comparison is commentary, not a benchmark, so don't present it as measured data.

It is the clearest example of a DTC product post framed around municipal operations rather than software features.

The post starts with the calendar that governs municipal work: billing cycles, reporting requirements, permit renewals and public meetings — a long list where missing a deadline has real consequences.

• DTC's Master Calendar is presented as one place to manage recurring jobs and deadlines.
• Billing runs can be scheduled, copied from year to year and tracked so nothing slips when staff are out or roles change hands; the whole team works from the same schedule instead of one person's inbox.
• The post closes with an invitation to reach out and see how it works.
• This is direct product promotion, not analysis.

For brands planning a campaign

Shows this creator's promotional register — problem, product, call to action — so a partner can plan for that format rather than an editorial one. Relevant if content is meant to sit alongside DTC's own tools, but a product post does not establish that any placement was paid.

Mark says one thing "April" reinforced for the team: the bar for what residents expect from local government online is not going down.

• A modern municipal website and an integrated self-service portal are no longer nice-to-haves but the baseline for a digital presence that works.
• DTC builds and hosts municipal websites and provides the Citizen Action Center as a connected self-service solution, so a municipality can meet residents where they already are.
• The post closes with an invitation to visit diversifiedtechnology.com or send a message to set up a conversation.
• The reference to "April" is not explained — no role, context or connection is given, which leaves a gap for a reader who does not already know the team.

For brands planning a campaign

The clearest statement of the digital services offering, with resident expectations as a framing that works well in campaign messaging. Ask the creator to clarify the unexplained "April" reference before citing the post publicly.

It shows the tone they use outside a pitch — useful when a collaboration should sound like the creator, not a product notice.

A short post thanking the municipalities and utilities that trust DTC with their operations.

• Clients manage real communities, infrastructure and residents' expectations that things simply work; Mark says the responsibility and the software's role in meeting it are not taken lightly.
• "We build what we build because the work our clients do matters."
• The post thanks existing clients and invites others to let DTC earn their trust.
• It is goodwill messaging, with no product, feature or metric.

For brands planning a campaign

A useful tone reference for trust-and-endorsement language without product claims — a model for campaigns that want the creator's voice without a hard pitch. It contains no outcome data, so don't use it to support claims about client results.

An automotive-parts analogy shows how cheap initial purchases can lead to workarounds, retraining and second implementations. They advise municipalities to calculate the staff-time cost of their current process before signing a contract.

Uses a cross-industry analogy to make procurement risk concrete.

For brands planning a campaign

A govtech vendor competing on value rather than price could create content that helps buyers identify hidden costs and counter low-bid competitors.

Examples: Source 1

They suggest municipalities ask three questions before signing: Can we export our data?

• What happens if the vendor is acquired?
• How long will implementation take, and who will do the work?

Frames vendor evaluation around three direct due-diligence questions.

For brands planning a campaign

A vendor with strong data portability and transparent implementation could position both as trust signals in content addressing procurement fears that stall deals.

Examples: Source 1

They argue it prevents missed tasks when staff are out or roles change.

For brands planning a campaign

For a utility operations or scheduling software vendor, Mark Anthony F. can demonstrate how centralized deadline management addresses a specific problem. The content is product-forward and tied to a specific tool.

Examples: Source 1

They point to DTC's website hosting and Citizen Action Center as ways to meet residents where they are.

For brands planning a campaign

A digital services provider could frame online services as a resident expectation, an angle suited to vendors selling constituent experience platforms.

Examples: Source 1

They frame the lack of IT staff as a superpower that enables early adoption.

Contrasts small-town and big-city decision-making to highlight a specific buyer segment.

For brands planning a campaign

A vendor targeting small towns could celebrate agility and fast deployment, appealing to buyers overwhelmed by enterprise-scale sales processes.

Examples: Source 1

They invite non-clients to consider earning that trust.

The post shifts from analytical problem-solving to relationship-building content.

For brands planning a campaign

A vendor seeking to humanize its brand or highlight customer relationships could use a similar expression of gratitude to position itself as a partner, not just a supplier.

Examples: Source 1

They use a first-person company voice and invite readers to contact DTC, but don’t clarify Mark Anthony F.’s relationship with the company. Ask whether they own, work for, or partner independently with DTC.

View example

Both creators treat the procurement document as a decision point that shapes what follows.

Andrew S. focuses on parking-program requests for proposals and the way they frame tasks versus outcomes. Mark Anthony F. examines software exit terms, data portability and the real operating cost after a contract is signed.

Read original · Original 2

Santosh Sabnis builds structural-audit arguments from termination records and named accuracy failures, including ALPR false positives and municipal AI chatbots without governance policies. Mark Anthony F. instead offers buyer-facing due-diligence questions and cost-of-ownership warnings, rather than audit histories.

Read original · Original 2

Chad Smeltzer draws examples from sewer and manhole inspection technology and from positioning civil-engineering firms upstream of procurement. Mark Anthony F. focuses on municipal software procurement, utility scheduling and resident digital services.

Read original · Original 2

The two posts argue that legacy parking RFPs reward vendors who preserve the old model and that a modern RFP should define outcomes like improved compliance and digitized permit administration rather than task lists like patrol hours.

• That is a direct fit if the vendor wants to be positioned as an alternative to outdated procurement language, not just as a better software choice.
• Their posts focus on the buying decision—three questions to ask before signing and why a low bid gets expensive—but do not dissect the RFP as a document that controls the outcome.

The tradeoff is scope: Andrew S.'s posts focus on parking programs and public contracting, so a campaign about municipal software procurement more broadly would need to adapt the framing rather than reuse it. The posts are longer analytical lists with bulleted assumptions, not the short analogy-plus-three-questions format they use, which changes the deliverable shape.

Examples: Source 1 · Source 2

The posts use a documented ALPR false-positive rate and a set of 82 termination records to argue that the contract, not the camera, determines whether a city keeps control of its data.

• They call for pre-vote data sovereignty audits, accuracy floors, and post-termination destruction requirements, and connect the same accountability gap to AI chatbots in city government.
• That is a stronger fit than they are if the vendor's message is about governance safeguards, independent verification, and what happens after termination, rather than a checklist for evaluating a software purchase.

The tradeoff is tone and focus: these posts offer a structural critique of procurement and civil service, so a collaboration would frame the vendor as fixing governance failures rather than as a practical buying guide. The format is a dense policy argument with numbered structural fixes, which is harder to adapt into a short partner post than their question-and-answer style.

Examples: Source 1 · Source 2

One post walks through a manhole inspection cost comparison—$500 per manhole with manual methods versus $125 with optical scanning—and argues that the old process persists because specifications and procurement have not changed.

• The other argues that engineering firms should build proprietary data, workflows, and diagnostics so owners come to them before procurement starts.
• That is a fit if the vendor wants to sell technology plus engineering judgment and move upstream of the RFP, not if the campaign is about choosing a municipal software vendor.

The tradeoff is category: the examples are infrastructure inspection and civil engineering services, so a municipal software procurement collaboration would need to translate the argument rather than reuse it.

• The posts include specific cost figures that are the creator's own estimates; verify them before repeating them in a partner post.
• They are longer narrative posts with numbered benefits, not the reusable short-post format they use.

Examples: Source 1 · Source 2