A GIS consulting proposal is the document a provider submits to define the scope, deliverables, timeline, and cost of a geospatial project. A strong proposal states the problem clearly, lists specific ArcGIS deliverables, sets a realistic schedule, and gives a transparent price, so you can compare vendors and approve work with confidence.
What a GIS Consulting Proposal Is For
A proposal is where a vague need becomes a concrete plan. It protects both sides. For you, it pins down exactly what you are buying and what it costs. For the provider, it defines the boundaries of the work so scope does not drift. When you read a proposal, you are really reading how well the vendor understood your problem.
The best proposals are specific. The weakest ones are full of capability statements and short on deliverables. If you cannot tell what you will actually receive, the proposal is not finished.
The Sections Every Strong Proposal Includes
Problem Statement
The proposal should open by restating your problem in its own words. This shows the vendor listened. A provider who jumps straight to their services without framing your situation has skipped the most important step.
Scope and Deliverables
This is the heart of the document. It should name specific outputs, not vague activity. A clear scope reads like a checklist you could verify on delivery.
- A defined StoryMap with a stated number of sections and data sources.
- A geodatabase design with attribute domains and attribute rules.
- A configured dashboard or an Experience Builder application with named functions.
- A spatial analysis with a described method and output.
Approach and Methodology
Here the vendor explains how they will work. Look for an approach that leads with ArcGIS Online before heavier deployments, and that favors out-of-the-box Esri tools over custom code. The methodology tells you whether the result will be maintainable after the engagement ends.
Timeline and Milestones
A realistic schedule with milestones lets you track progress. Be wary of timelines that are either implausibly fast or open-ended. Each milestone should tie to a deliverable you can review.
Pricing
The price should be clear and tied to the scope. Fixed-scope pricing is far easier to approve than open-ended hourly billing, because you know the ceiling before you start. A vendor that publishes pricing has already removed the biggest source of friction.
Team and Credentials
The proposal should name who will do the work and summarize their relevant expertise at a high level, such as a Certified ArcGIS Expert leading delivery. What matters is that senior capability is doing the actual work, not just pitching it.
| Section | Strong Proposal | Weak Proposal |
|---|---|---|
| Problem statement | Restates your situation specifically | Generic intro about the vendor |
| Deliverables | Named, verifiable outputs | Lists of activities, no outputs |
| Timeline | Milestones tied to deliverables | No dates, or implausible speed |
| Pricing | Fixed scope with a clear total | Open-ended hourly, no ceiling |
How to Get a Better Proposal
Proposals are only as good as the brief behind them. Give every vendor the same clear brief and you will receive proposals you can actually compare. A strong brief states the decision the work supports, the data you have, the audience for the result, and your budget range. Our guide on how to hire a GIS consultant covers how to build that brief before you request anything.
When the proposals come back, score them with a consistent framework rather than reacting to the most polished one. Our approach to evaluating GIS consulting firms pairs well with proposal review, because the document and the firm behind it should be judged together.
Reading the Price in Context
A low number is not automatically a good deal, and a high number is not automatically thorough. Read the price against the deliverables. A proposal that quotes less may simply include less. The clearest way to budget is to understand the general market ranges for each type of engagement, then map them to a provider’s scope. GeoLever’s productized engagements map to three common project types.
- GeoStory: Esri StoryMap development. Across the market, GIS StoryMap projects typically range from $2,500 to $7,500. GeoLever offers a productized StoryMap-in-a-Week, starting at $3,500 (geolever.co/start).
- GeoConsult: ArcGIS platform consulting. Platform consulting engagements commonly run $5,000 to $15,000 per project across the industry.
- GeoPartner: embedded geospatial consulting. Embedded, retainer-style geospatial engagements across the market commonly run $10,000 to $25,000 per month.
For GeoConsult and GeoPartner work, GeoLever scopes and quotes each engagement within 48 hours of a 30-minute discovery call. For more on what moves a quote up or down, see our breakdown of GIS consulting cost.
Red Flags in a GIS Proposal
- No clear deliverables, only activities and effort.
- Open-ended pricing with no ceiling or fixed scope.
- A timeline with no milestones to review against.
- Custom development proposed where configuration would do.
- No named team or proof of comparable past work.
A Sample Proposal Walkthrough
It helps to see how the sections fit together in practice. Imagine a county parks department that wants a public-facing map of its trail network plus a StoryMap for an upcoming funding request. A strong proposal for that work would read roughly like this.
It opens by restating the department’s situation: an aging trail inventory, no easy way for the public to find trails, and a grant deadline approaching. The scope then names two specific deliverables, a hosted web map of all trails with filtering by difficulty and length, and a StoryMap with a stated number of sections built around the funding narrative. The approach explains that the data will be organized in a geodatabase with attribute domains so trail attributes stay consistent, that the public map will be configured in ArcGIS Online, and that the StoryMap will pull from the same authoritative layers. The timeline sets three milestones tied to those deliverables. The pricing lands inside the typical market range for a StoryMap project, because the StoryMap is the centerpiece. The team section names the Certified ArcGIS Expert leading the build.
Every section answers a question the buyer would otherwise have to ask. That is what a finished proposal does.
How to Read the Methodology Section
The methodology is where a proposal reveals whether the result will last. Two providers can promise the same deliverable and arrive at very different long-term costs based on how they build it. Look for three signals.
- Platform ordering. A strong methodology leads with ArcGIS Online and reaches for ArcGIS Enterprise only when on-premise control is genuinely required. Leading with the heaviest option inflates cost and complexity.
- Configuration over code. Applications built with out-of-the-box tools like Experience Builder and Field Maps stay maintainable. Custom code becomes a dependency that someone has to support for years.
- Data foundations. A proposal that mentions geodatabase design, attribute domains, and attribute rules is thinking about the long-term health of your data, not just the immediate deliverable.
From Approved Proposal to Working Project
Approval is the start of the work, not the end of the decision. A clean transition keeps the early momentum. Confirm the kickoff date, the review cadence, and who your point of contact is. Make sure the data handoff is scheduled, because most delays trace back to source data arriving late. Agree how scope changes will be handled, so a mid-project adjustment does not turn into a budget dispute.
A good provider will already have a process for this transition and will walk you through it without prompting. If you are still comparing options at this stage, our guides to GIS consulting services and what they include can help you confirm the scope matches your need before you sign.
Why Fixed-Scope Proposals Reduce Risk
The single biggest difference between proposals that go smoothly and proposals that end in friction is how they handle scope and price. An open-ended, hourly proposal pushes all the risk onto you. The final cost is unknown until the work is done, and there is little incentive for the provider to be efficient. A fixed-scope proposal flips that. The provider commits to a defined deliverable for a defined price, which means the planning discipline happens up front, where it belongs.
Fixed scope also makes comparison honest. When three vendors quote a fixed price for the same brief, you are comparing like with like. When they quote hourly rates against vague effort estimates, you are comparing guesses. The hourly option can even look cheaper on paper while costing more in practice, because the estimate was optimistic.
This is why published pricing is more than a convenience. It signals that a provider has done this work often enough to know what it takes, and it sets expectations before the proposal stage rather than after. A proposal that arrives with a clear ceiling is a proposal you can take to a budget holder and get approved without a round of nervous questions.
Need a clear GIS proposal you can actually approve?
Share your brief and we will return a scoped proposal with named deliverables and fixed pricing within 48 hours of a short discovery call.
Frequently Asked Questions
What is a GIS consulting proposal?
It is the document a provider submits to define the scope, deliverables, timeline, and cost of a geospatial project. A strong proposal restates your problem, lists specific ArcGIS deliverables, sets a realistic schedule, and gives transparent pricing.
What should a GIS consulting proposal include?
A problem statement, a clear scope with named deliverables, the approach and methodology, a timeline with milestones, transparent pricing, and the team and credentials. Each deliverable should be specific enough to verify on delivery.
How do I compare GIS proposals from different vendors?
Send every vendor the same brief, then score the returned proposals on deliverables, timeline realism, pricing clarity, and proof of past work. Identical briefs make differences in approach and price easy to see.
What is a red flag in a GIS proposal?
Watch for missing deliverables, open-ended pricing with no ceiling, a timeline without milestones, custom development where configuration would do, and no named team or proof of comparable work.
How much should a GIS project cost?
It depends on scope. Across the market, GIS StoryMap projects typically run $2,500 to $7,500, platform consulting engagements commonly run $5,000 to $15,000 per project, and embedded, retainer-style models commonly run $10,000 to $25,000 per month. GeoLever offers a productized StoryMap-in-a-Week starting at $3,500, and scopes and quotes other engagements within 48 hours of a 30-minute discovery call.
