Maryland now asks agencies to bring the problem, not the product. Here's a tech request written that way
"We need a new CRM" is how a lot of government technology requests start, and Maryland's IT department has decided that's the wrong first line. Its new intake asks what the agency is trying to accomplish before anyone talks about a product. That's a useful habit far beyond Annapolis, so here's what a rewritten request looks like.

Maryland's Department of Information Technology now routes every agency technology request through one intake and a new technical acquisition team that asks what problem the agency is solving before it picks a product or contract. Any public agency can borrow the habit: describe who is affected, what happens today, what better looks like, what you already own and what can't change, and leave the product name out of the first page.
What Maryland changed
Maryland's Department of Information Technology has rebuilt how state agencies ask for technology. The new framework, announced by Secretary and State CIO Katie Savage at the start of November, sends every request, from a single laptop to an electronic health record system, through one intake, which Savage calls a "single front door."
Behind that door is the state's first dedicated technical acquisition team: procurement professionals working alongside software engineers, product managers, user experience researchers and designers. Their job is to understand what an agency needs, look at possible solutions and check whether something the state already owns would do before anyone buys anything new.
This week, GovTech reported that Maryland's DoIT has also become the first state customer of Marketplace.city's Clearbox, a vendor research tool that more than 130 cities already use to compare pricing, contracts and references.
The changes carry out Maryland's Procurement Reform Act of 2025, which took effect on October 1, and the governor's wider procurement agenda.
The numbers behind the change, as reported by StateScoop, are striking. Discovery work in fiscal 2026 found more than 1,700 technology requests representing over $500 million in estimated demand. Only about 3% of the combinations of buy type and procurement vehicle had a template, and some requests for proposals ran to 118 pages stitched together from older documents.
The CRM example
Savage gave an example that will sound familiar to anyone who has worked in public sector technology. An agency asks for a new customer relationship management system. Under the old intake, the main question was whether an existing contract could be used.
Now the team asks something else first: "Let's unpack why you think you need a CRM system. Like, what are you actually trying to accomplish?" Sometimes, she said, a CRM isn't the right answer. Sometimes it is, but the agency also needs work around it to make it useful.
A request that names the product has already skipped the most useful conversation. It's also how a $40 million project gets proposed for a problem that, in Savage's words, "you might actually be able to solve with something much cheaper."
Decision guide
The same request, two ways
| Consideration | Product-first request | Problem-first request |
|---|---|---|
| First line | We need a new CRM | Business owners wait weeks to hear back about license questions |
| Who is affected | Not stated | Applicants, four licensing staff, the call center |
| What happens today | Not stated | Email inbox, a spreadsheet, callbacks from personal phones |
| What better looks like | Modern system | Every question has an owner and an answer date the applicant can see |
| What we already have | Not considered | Statewide case tool, existing call center software |
A request that names the product has already skipped the most useful conversation.
The request, rewritten
Here's an illustrative example, a composite rather than a real Maryland document.
The original request: "The licensing division needs a new CRM to manage applicant communications. Budget estimate attached."
The rewritten request:
Who is stuck. Small business owners applying for a state license, the four staff who process applications and the general call center that takes their calls.
What happens today. Questions arrive by email to a shared inbox. Staff track them in a spreadsheet. When an applicant calls, the call center can't see the spreadsheet, so it takes a message. Staff call back from their own desk phones, sometimes days later. Nobody can say how many questions are open.
What better looks like. Every applicant question has an owner and an answer date the applicant can see. The call center can see the status of an application while the person is on the phone.
What we already own. The state's case management platform, the call center's existing software and the licensing system itself, which already has applicant records.
What can't change. The licensing rules and statutory deadlines, the requirement to keep certain records, and a launch before the spring renewal season.
Read that way, the answer might be a CRM. It might also be a shared queue in a system the agency already owns, a status page connected to the licensing system and a change to how the call center is set up. The point is that the team reviewing it can tell.
Why this helps the agency, not just procurement
Savage acknowledged that agencies may see the new process as more paperwork. In practice, a problem-first request often saves time, because it lets reviewers say yes to the smaller, faster option instead of sending a large purchase through a long procurement.
It also changes what vendors see. A solicitation that describes the problem invites proposals that solve it. One that describes a product invites proposals that sell it. If you've ever had three bids that all answered the wrong question, this is usually why. Our note that a comparison table is not a decision makes the same point from the buyer's side.
There's a cost argument too. A request written around a product tends to get priced around that product, with licenses, implementation and training bundled in. A request written around the problem can be split: fix the call center routing this quarter, connect the status page next, and decide on a bigger system only if those don't do enough. Each piece is smaller, easier to approve and easier to stop if it isn't working.
Tools like Clearbox point the same way. Being able to see what peer agencies bought, what they paid and which vendors they used is far more useful when you know which problem you're comparing.
And it protects the people at the end of the process. Residents don't experience a CRM. They experience waiting for a callback. Starting with what they go through, as in start with the handoff, keeps that in view all the way to launch.
How the work moves
Five lines before any product name
- Who is stuck
Name the residents, businesses or staff who feel the problem.
- What happens now
Describe one real case from start to finish, with the handoffs.
- What better looks like
Say what a person could do afterwards that they can't do today.
- What you already own
List the systems and contracts that might already cover part of it.
- What can't change
Rules, deadlines, data limits and the date it has to work by.
Borrow it, wherever you are
You don't need a new state law to do this. Any agency, city department or school district can adopt the five lines before the product name: who is stuck, what happens now, what better looks like, what you already own and what can't change. Put them on the first page of every technology request and see how many requests change shape.
If you're a vendor, read requests the same way and ask the questions the request didn't answer before you write a proposal. A short call to ask "what happens today?" is usually the most valuable hour in the whole bid, and agencies tend to remember who asked it.
If you're on the reviewing side, send back requests that lead with a product and ask for the five lines first. It feels slower for a week and saves months later.
Where we help
We help public agencies turn a problem into a scoped, buildable plan, including working out when the answer is a smaller change to something already in place. That's our government and public sector work. Talk to us.
Related work: Sutton|Place
We build alongside the people doing the work.
Bring us the problem you’re thinking about.