Andrew S.

The document, not the toolkit, tells vendors what matters. Andrew S. argues that innovation is filtered out before real competition begins, and the evaluation criteria favour proposers best at answering yesterday's questions.

A post describes an agency that publicly states it wants customer convenience, data transparency and stronger compliance, then issues an RFP built on decade-old assumptions—a signal that preserving the old model ranks above improving it.

Read original · Original 2 · Original 3

Andrew S. says agencies are puzzled when a replacement contract resembles the one it replaced, and treats that as the expected result of the procurement document: it told vendors exactly what mattered, and it was not meaningful change. The question is not whether better tools exist—the posts say they do—but whether the framework lets anyone propose them.

One post closes its reasoning with the line 'the procurement told vendors what mattered,' then observes that agencies are surprised when their new contract looks so much like the old one.

Read original · Original 2

Andrew S. contrasts a parking RFP written as a shopping list of tasks—provide patrol, issue citations, manage permits, answer phones—with a scope written around desired results.

• In their account, task-based documents buy activity rather than performance, lock the agency into a potentially obsolete management model, and measure success by inputs such as patrol hours rather than outcomes such as improved compliance or reduced customer friction.
• An outcome-shaped document challenges the market to improve compliance, digitize permit administration, strengthen revenue controls, deliver actionable operational intelligence and offer a scalable modernization roadmap.

The post moves from a named task list (patrol, citations, permits, phones) to a named results list (compliance, digitized permits, revenue control, operational intelligence, modernization roadmap), making the proposed replacement as specific as the problem.

Read original · Original 2

Together, these assumptions filter out innovation before competition starts.

The post lists all five as bullets—'labour over technology,' 'tasks over outcomes,' 'continuity over experience,' 'reporting as an afterthought,' 'replication over improvement'—and frames them as assumptions embedded in the document before any vendor responds.

Read original

They argue that the problem is not a shortage of new tools or better service models, but a procurement framework designed—deliberately or not—to reward vendors for answering yesterday's questions. Their priority: parking procurement must catch up with parking practice.

The sectors are operating contexts Andrew S. says they have worked through, not named clients or projects. Ask for case studies or measured outcomes if those are important to your decision.

Read original · Original 2

The shortest version gives the thesis without supporting reasoning: municipalities say they want innovation, their RFPs ask for continuity, decade-old assumptions filter out modernization before competition begins, and the problem is old procurement language rather than old technology. Repetition across posts suggests a settled position, and the phrasing travels well in short form.

One four-sentence post carries the whole claim, closing with a contrast between old procurement language and old technology.

Read original · Original 2 · Original 3

This is the best entry point for readers who want the full argument.

The most complete post lays out the argument in a list.

• Andrew Sachs says the limiting factor in a municipal parking program is not aging equipment but the assumptions carried in the RFP itself, and names five: labour treated as the core of parking rather than technology-enabled management; responsibilities written as narrow task lists instead of performance goals; administrative continuity ranked above customer experience; reporting treated as a back-office formality rather than a management tool; and replication of the current program set as the goal instead of asking the market to improve it.
• The claim is causal: the document tells vendors what matters, so proposers who answer yesterday's questions win, and the next contract looks like the last one.

For brands planning a campaign

A vendor bidding on a legacy-scoped RFP can use this list to diagnose the response: name the assumption the agency's document carries, then show what an outcome-shaped alternative would measure. It also supports pre-RFP outreach, making the argument to the agency before the document is fixed.

The clearest statement of the alternative.

• Andrew Sachs argues that a parking RFP scoped as a shopping list of tasks — provide patrol, issue citations, manage permits, answer phones — buys activity rather than results, locks the agency into a management model that may already be obsolete, and measures success by inputs such as patrol hours instead of outcomes such as improved compliance or reduced customer friction.
• The proposed replacement is explicit: define desired results, and ask the market to improve compliance, digitize permit administration, strengthen revenue controls, deliver actionable operational intelligence, and provide a scalable modernization roadmap.

For brands planning a campaign

Useful as the basis for a counter-proposal section. A vendor can restate the agency's task list as outcome commitments with attached measures, reframing the evaluation from headcount offered to improvement delivered.

This is the tightest statement of the procurement-versus-technology distinction.

A shorter version of the same thesis, with an added framing line: in parking, innovation is a procurement problem long before it is a technology problem.

• The post describes an agency that says it wants customer convenience, data transparency and stronger compliance, then issues an RFP built on assumptions from a decade ago, signalling that preserving the old model matters more than improving it.
• The evaluation criteria then favour proposers best at answering yesterday's questions, which the post offers as the reason new contracts resemble old ones.

For brands planning a campaign

Frames the procurement document as the first competitive filter. A vendor's go-to-market positioning can lead with procurement-language expertise rather than product features: the argument is that the document, not the technology, decides who can win.

Read this post for the scope of the claim.

This post adds a claim of range.

• Andrew Sachs writes that the same pattern has appeared across the private sector, municipal government, transit and higher education, and describes having worked through those different operating lenses.
• The conclusion is that the problem is not a shortage of new tools or better service models but a procurement framework designed, deliberately or not, to reward vendors for answering yesterday's questions.
• It ends with the line that parking procurement must catch up with parking practice.

For brands planning a campaign

Supports positioning a vendor's procurement expertise as transferable across public and institutional buyers, not just one city department. The list of sectors signals a claimed pattern, not a documented client list; ask for references before treating it as a record of client experience.

Readable in seconds if the longer posts aren't needed.

A four-sentence condensation of the same argument: municipalities say they want innovation, their RFPs ask for continuity, decade-old assumptions filter out modernization before competition begins, and the problem is old procurement language rather than old technology. A shortened link closes this post, as it does the others.

For brands planning a campaign

Usable as a quotable summary for slides or outreach, though it adds no reasoning beyond the longer posts and should not be cited as separate evidence for the same claim.

When an agency releases an RFP built on decade-old assumptions, they argue, it tells the market that preserving the old model matters more than improving it, so vendors best at answering yesterday's questions win. Three posts restate the idea in slightly different words, making it the clearest recurring position in the posts.

The argument recurs across short posts with small variations, so it reads as a settled position rather than a developing one.

For brands planning a campaign

A parking technology vendor should open with procurement diagnosis rather than product features when engaging this creator, and be ready to show how a rewritten RFP scope would change which suppliers can compete.

Examples: Source 1 · Source 2 · Source 3 · Source 4

Sachs says task-based documents measure inputs like patrol hours and lock agencies into management models that may already be obsolete, while outcome-based scopes invite vendors to propose more efficient, technology-driven approaches.

Paired contrasts and concrete task examples make the distinction easy to repeat in conversation and copy.

For brands planning a campaign

A vendor can supply sample outcome-based RFP language as a proof asset: the same agency and requirements, rewritten from inputs to measurable results.

Examples: Source 1 · Source 2

The post frames these as assumptions baked into legacy procurement documents that filter innovation out before real competition begins.

A short bulleted diagnostic, the only item in the posts that enumerates the pattern rather than describing it.

For brands planning a campaign

Use the five-point list as an audit framework in content or sales conversations, walking an agency through which of the five assumptions its current RFP carries.

Examples: Source 1

Sachs presents it as a consistent pattern observed across those settings.

Ask for case studies, client names, or performance figures to assess documented experience beyond perspective.

For brands planning a campaign

Position this creator as a procurement-pattern commentator for public-sector audiences instead of marketing the profile on named credentials or results the public material does not supply.

Examples: Source 1 · Source 2

Two other posts open by framing procurement as the earlier and more decisive issue than technology.

The argument is repeatedly compressed into a single sentence, suggesting the phrase travels well in short-form posts.

For brands planning a campaign

One-line copy naming the continuity trap is likely to match how this creator frames the subject and how the audience is used to receiving it.

Examples: Source 1 · Source 2 · Source 3

They show no other recurring subjects, formats beyond short opinion posts, or commercial integrations and partnerships.

The sample is five posts, several of them close restatements, and no publication dates were provided, so the absence of other topics here is not evidence that none exist elsewhere.

For brands planning a campaign

Expect a focused procurement-reform conversation. Ask for examples of broader creator-led formats if the campaign needs them.

Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5

Both build short LinkedIn posts around a single contrast, arguing that the upfront decision—the contract, bid rules or vendor relationship—matters more than the tool that arrives afterward.

Mark Anthony F. focuses on cost and lock-in: the lowest bid that leads to workarounds, total cost of ownership measured against staff time, and data-portability questions to ask before signing a software contract. Andrew S. focuses on solicitation language and parking, arguing that task-based RFPs filter out better proposals.

Read original · Original 2

Both argue that compliance and workforce obligations are deliverables, not paperwork, drawing on experience across several public and private operating contexts.

Danielle Lares works on skilled-trades workforce pipelines, apprenticeship placement and federal reporting for infrastructure and energy projects.

• Their systems-alignment approach connects owners, contractors, unions and educators.
• Andrew S. focuses on municipal parking procurement and RFP structure.

Read original · Original 2

Andrew S. describes the same mechanism: procurement rules tell the market what the agency values.

Menkhaus is an engineer working on water and wastewater projects under progressive design-build, and writes longer explanations of specific procurement practices. Andrew S. makes brief, recurring arguments about parking RFPs and task-versus-outcome scoping.

Read original · Original 2

The two posts argue that a lowest-bid municipal software contract often produces a second, unofficial system that staff build around the one they bought.

• They measure the cost through the agency's current process—staff hours per month—rather than the software price.
• The second post frames vendor lock-in through three questions to ask before signing: Can the agency export all of its data in a standard format at any time?
• What happens to that data if the vendor is acquired?
• How long does implementation take, and who does the work?
• For a parking technology vendor whose prospect is stuck in an incumbent contract, or whose bid has to beat a cheaper one, that cost-of-ownership and lock-in argument speaks directly to the buying moment.

The focus is narrower and comes one step later in the cycle.

• Mark Anthony F. writes about the commercial structure of a software purchase, not the RFP document itself.
• A campaign would gain a renewal and replacement argument but lose the diagnostic of stale RFP assumptions and the outcome-language rewrite that Sachs supplies.
• Two posts draw on prior automotive and municipal software experience.

Examples: Source 1 · Source 2

The posts examine selection methods: best-value procurement rewards firms that keep past clients happy because reputation drives the next award, while hard-bid lets a firm cut corners and still win.

• They also argue that one-on-one proprietary meetings between an owner and each proposing team tend to raise proposal quality and make the process more defensible, not less.
• A vendor selling into an agency that is choosing or revising how it selects a technology vendor can use that owner-side explanation of why an outcome or best-value structure suits the purchase better than a task list.

The sector and the seat are different.

• The examples come from water and wastewater design-build capital projects, and Will Menkhaus writes from the owner's side of a progressive design-build procurement.
• That is the side the parking technology vendor is selling to, but it is not the same market or delivery model.
• Neither post contains a parking, software, or municipal technology example, so a campaign would borrow a procurement-design argument rather than parking-specific content.
• Evidence is two posts from June 2025, with no audience or format documentation.

Examples: Source 1 · Source 2

The posts treat compliance as part of the deliverables rather than a separate administrative track, connecting apprenticeship, DOT oversight, funding eligibility, and project delivery. One post frames workforce supply as a question of matching skills to the phases of work rather than counting available workers.

This is a different buyer task.

• The subject matter is skilled-trades workforce pipeline, apprenticeship, and DOT labor compliance for infrastructure and energy projects; the audience is contractors, unions, owners, workforce partners, and funding partners.
• Neither post deals with procurement documents, RFP evaluation, or software selection, so for a parking technology vendor selling to municipal parking agencies, the material does not answer the same question Andrew Sachs answers.
• It fits only where workforce compliance is a real requirement of the program being sold into.

Examples: Source 1 · Source 2