01
Operating budget development
Department request entry, multi-year actuals pull, county-wide rollup without spreadsheet consolidation, versioning, and in-platform leadership review.
Pre-bid brief · Live RFI · Under NDA 
A prime's pre-bid brief for Adams County RFI-RZA-2026.560.
Adams County, Colorado, a cloud-based budgeting platform across the full budget lifecycle. This is a Request for Information, no award and no contract. Techtiz writes the response and builds the platform behind a US prime who owns the agency relationship.
Live · responses close Jun 22, 3 PM MT
Awarding body Adams County
Jurisdiction Colorado
Status Responding under NDA
Solicitation
RFI-RZA-2026.560Request for Information
Scope
Cloud budgeting platformFull budget lifecycle
Stage
No awardInformation-gathering only
Techtiz role
Back-officeNDA-first, never agency-facing
Schedule of events
One response deadline, no late entries.
A formal RFI. Written questions go to the contact by June 12. Responses are accepted electronically only, through the platform, and anything after 3:00 PM MT on June 22 is not accepted.
Issued
Published on the platform, 12:39 PM EDT
Questions due, 5 PM MDT
By email to Rebekah Zamora-Arroyo
Responses due, 3 PM MT
Electronic only via ccionline.org. No late entries
LivePossible RFP
A future RFP may follow, not guaranteed, subject to County budget approval
25 days from issue to response, tight for an RFI of this scope. Today the clock is running.
The RFI-to-RFP pathway
No award here. The prize is shaping the RFP that may follow.
This is information-gathering. Reading it any other way wastes effort or anchors a future bid badly.
What this isA Request for Information, not an IFB or RFP. No award is made, no contract is signed, and no pricing is binding. Responses gather market input.
What may followA future RFP is possible but not guaranteed, and any RFP would carry its own County budget approval and a separate competitive process.
Why respond wellThe County has not decided between an enterprise platform and a specialist tool. A clear, county-specific response shapes the eventual RFP scope and makes the responder a known quantity before the committee assembles.
How to submitElectronic only, through the ccionline.org platform, in a two-envelope format: Envelope 1 Identity and Proposal, Envelope 2 Pricing. The contracting entity for any future contract is Adams County through the Board of County Commissioners.
Scope · The differentiator
ERP integration is the most technically specific clause in this RFI, and the County's ERP is not named.
Three data flows define the fit: actuals pulled near real time for budget-to-actual, chart of accounts periodically, and position data event-driven. Identifying the County's ERP before responding is the largest single advantage available; comparable Colorado counties run Tyler, SAP, or Oracle environments. The close second is the 10-year CIP and long-range planning horizon, which narrows the real field well below the 55-plus downloaders, because many platforms stop at a 5-year window. Domain understanding shows by naming the ERP concretely, not by checking a feature box.
This integration and data-engineering work is exactly what Techtiz builds behind the prime, in vendor-hosted or synthetic environments, never against county systems.
Task allocation
What a remote engineering team can build, and what stays onshore.
The boundary that keeps a Subcontracting model clean on a public-sector data engagement.
Practical, not statutory. This RFI contains no offshore restriction and no NDA requirement, which is expected for an information-gathering document. The gates here are forward-looking. County IT will not grant offshore access to internal systems, any work involving county data is handled by the US prime or US-based team members, and the prime owns the relationship under a mutual NDA. At the RFI stage almost no county data is in play, so the offshore lane is wide. The gates bind once county data and ERP access enter at the RFP and contract stage.
Remote engineering & back-office Subcontracting
Pre-production, no county data
Read and index the full RFI
Draft the response sections that map each capability area to a platform feature
Research the County's unnamed ERP through public records and vendor rosters
Develop the indicative pricing range with low, mid, and high scenarios and flagged assumptions
Prepare comparable county-government reference summaries from the prime's own client data
Draft the SSO description naming identity providers and protocols, SAML 2.0, OAuth 2.0, OpenID Connect
Prepare the demonstration environment on vendor-hosted or synthetic data
Build and configure the platform against synthetic or vendor-hosted environments
Techtiz operates only in this column, behind the prime, under a mutual NDA, never touching county systems or county data.
US prime only
Onshore, accountable, county data
Any access to the County ERP environment
Any handling of county financial data
Direct communication with Adams County
Signing and submitting the response on the platform
Holding any future contract as prime
Gates, stated plainly. A mutual NDA covers the RFI contents, the internal pricing and strategy, and the analytical work product, with a term of at least three years, governed by the law of the prime's state of incorporation, not offshore law. No offshore access to county systems or county-proprietary data at any stage. The prime reviews and submits all client-facing material.
Where responses fail
Nothing here is disqualifying. Each one quietly costs the future RFP.
An RFI has no scoring, so none of these is pass or fail. They are the moves that get remembered when the RFP committee assembles.
Treating the RFI as a binding proposal RFI nature
The miss
Responding as if this were an RFP, with firm commitments and over-built detail, mistakes information-gathering for a competition.
The cost
Over-investing as if an RFP were guaranteed burns effort. Calibrate the response to shape the RFP, not to win a contract that does not exist yet.
Where emphasis lands
No formal scoring, but emphasis is readable.
An RFI carries no weights and no award. The split below is the Collab P analyst estimate of where a strong response should concentrate, not an Adams County criterion. Eligibility is simply qualified organizations with experience in public-sector budgeting software, and there are no pass-or-fail gates.
Collab P analyst estimate of emphasis, not an Adams County criterion
01System capability coverage~35%
02ERP integration & technical fit~25%
03Public-sector experience~20%
04Implementation approach~12%
05Pricing structure~8%
These percentages are an internal framing aid, not official weights. Where this estimate and the RFI differ, the RFI governs. The RFI itself states no scoring and makes no award.
Full scope
The full budget lifecycle, end to end.
The platform covers eight capability areas. ERP integration is the technical hook the whole response turns on.
02
Personnel & position budgeting
Salary and benefits modeling across years, step and cost-of-living changes, new-position costs, funded-versus-unfunded status, cross-fund allocation.
03 · 10-year horizon
Capital & CIP planning
Project entry, prioritization, multi-year carryforward and reappropriation, operating-impact capture, and a 10-year CIP outlook with visualization.
04 · 10-year horizon
Scenario planning & forecasting
What-if modeling, side-by-side scenario comparison, and 10-year long-range forecasting of operating budgets, personnel, capital, and fund balances.
05
Mid-year & off-cycle adjustments
Structured submission, routing, and approval, with a clear one-time versus ongoing distinction.
06
Reporting & dashboards
Budget-to-actual, variance, drill-down, dashboards, and a public-facing adopted-budget and capital-plan view.
07 · The hook
ERP integration
Pull actual expenditure data, chart of accounts, and position data from the County's ERP, reducing manual entry. The ERP is not named.
08
Single Sign-On
Organizational credentials via SAML 2.0, OAuth 2.0, and OpenID Connect. County IT treats SSO as a core security control.
Value & pricing
SaaS plus implementation, and one variable moves the future number.
No budget is stated, and no pricing is binding. The ranges below are Collab P pre-bid estimates derived from scope, not county figures. ERP integration cost is the variable that most affects a future win.
Low
$280-380k impl
Plus about $70k per year SaaS. Assumes a pre-built ERP connector and light customization.
Mid / most likelyBase case
$400-510k impl
Plus about $100k per year SaaS. Custom ERP integration, multi-year data migration, training for 50 to 100 county users. Model under NDA
High
$550-720k impl
Plus about $140k per year SaaS. Legacy decommission, a non-standard ERP, phased rollout, and heavy change management.
The key variable is ERP integration cost. A certified connector to the County's actual ERP drops that line from roughly $30,000-plus toward near zero, a swing worth more than any other efficiency. All figures are Collab P estimates, not county figures.
Envelope 2 is labeled lump sum, but submit an indicative range with explicit non-binding language. Do not attach a firm number; a hard price anchors the eventual RFP.
Techtiz back-office pricing is scoped per engagement after NDA and is not part of the public solicitation intelligence.
Security & standards
The security and standards a Colorado county expects.
Industry-standard security and public-sector data management, in the language county IT reads. Governing law is Colorado; any future RFP would likely cite Title 29 and County purchasing regulations.
SOC 2 Type II
The control-attestation baseline for a hosted public-sector platform.
WCAG 2.1 AA
Accessibility for the admin console and the public-facing budget view.
AES-256 & TLS 1.2+
Encryption at rest and in transit across the platform.
US-based hosting
A hosting preference that matters to a Colorado county buyer.
SSO via SAML / OAuth / OIDC
Single Sign-On on organizational credentials, treated as a core control.
Audit logging
Full audit trail for budget changes, approvals, and adjustments.
Backup & recovery
Data retention, backup, and recovery commitments described in the response.
Colorado law, Adams County venue
Colorado Revised Statutes Title 29 and County purchasing rules, venue in Adams County District Court. The municipal default; no code is cited in the RFI itself.
Agency context
Who is buying, and who scores it.
Adams County is a county government in the Denver metropolitan area, county seat Brighton, founded 1901. It buys through the Board of County Commissioners, with the Finance Department's Purchasing Division as the issuing office. Rebekah Zamora-Arroyo, Contract Specialist II, is the named contact and signer. The RFI gathers market input on a cloud budgeting platform; no award is made from it.
~519,572
Residents, 2020 census
Brighton
County seat, Denver metro
94629
NIGP budgeting services
Adams County Government Center, Brighton, Colorado. Photo via the County. Population figures are public-source estimates.
The competing field
34 primes mapped, a handful of global platforms carry the revenue.
From the prime-contractor database. A few enterprise vendors dominate the revenue total at parent-company scale, but the field runs long and the in-state presence is real. Figures are public-source estimates for partner targeting.
34
Firms mapped to the RFI
19 / 14
Highly / partially relevant
7
Colorado-based primes
~$407B
Combined est. revenue
10national / global, $1B+8large, $100M to $1B11mid-market, $10M to $100M3boutique, under $10M
The $407B total is dominated by parent-company revenue, not budgeting-line revenue: Microsoft Dynamics 365 about $280B, Oracle about $57B, SAP America about $42B, Workday about $9B, and Carahsoft about $8B. Read it as scale, not as money chasing this work.
More than 55 organizations downloaded the RFI within hours, from enterprise ERP vendors to specialist government-budget platforms, consultancies, and regional Colorado firms. The County has not chosen between an enterprise platform and a specialist tool, which is exactly why a clear, county-specific response can shape the RFP.
The 7 Colorado-based primes, the full named map, and the relevance scoring are in the full document pack. Ask us for it under NDA.
The response
Eight things the RFI asks every response to cover.
Map the response heading-for-heading to these. The pricing structure is high-level and non-binding at this stage.
01Public-sector budgeting experience02System overview mapped to the stated capabilities03Implementation & training approach04High-level pricing structure, indicative and non-binding05Similar-client examples06Unique strengths07SSO description08Any other helpful information
Before June 12
Six questions worth raising.
Questions the prime should consider, in writing, by the June 12 deadline. Keep them constructive and market-informing. Techtiz never contacts the County.
Question 01
Which ERP does the County run?
The unnamed ERP defines the single most technically specific clause and the biggest pricing variable.
Question 02
Is there a dedicated budgeting application today, and what are its limits?
What is being replaced shapes the migration and the implementation approach.
Question 03
How many departments and users?
User count drives both the SaaS line and the training program size.
Question 04
Phased implementation or full cutover?
The rollout model changes the timeline, the risk profile, and the change-management cost.
Under NDAQuestion 05
Is legacy data cleanup or migration in scope?
Multi-year historical migration is a major cost driver worth scoping early.
Under NDAQuestion 06
Enterprise platform or specialist tool?
The County is undecided. A constructive question here helps shape the RFP without overstepping.
Under NDA How Techtiz fits
The response engine and the build, behind your firm.
Techtiz writes the response and builds the platform in vendor-hosted or synthetic environments. The prime owns the ERP access, the county data, the submission, and every word said to the County.
Mutual NDA first
An NDA covering the RFI contents, the internal pricing and strategy, and the work product, for at least three years.
Draft the RFI response
Each capability area mapped to a platform feature, the ERP researched from public records, the pricing range built with flagged assumptions.
Build in safe environments
The demonstration environment and platform configuration on vendor-hosted or synthetic data, never against county systems.
Your firm owns the relationship
ERP access, county data, the platform submission, and any future contract all stay with the prime.
NDA Prime name and engagement scope stay under NDA. Techtiz never accesses county systems, the county ERP, or county financial data, and never contacts the County.
Responding to RFI-RZA-2026.560? The window is open.
Request the full RFI-decode pack.
Tender Insight, Tender Abstract, Summary of Procurement, the Statement of Work, and the U.S. primes database. A US partner manager replies within one business day, under a mutual NDA, never agency-facing.
Frequently asked questions
Pre-bid brief & confidentiality
Quick answers about how to use this engagement example and what detail is available under NDA.
Why is the prime contractor name withheld?
Most SLED subcontract work sits under mutual NDA and prime branding requirements. Public summaries describe engagement type, technical surface, and outcomes. Partner names and proposal content are shared only with explicit written permission or under an executed teaming agreement.
Can Techtiz support our bid on a similar pursuit?
Yes. If your pursuit matches this engagement type, email sled@techtiz.co or use the teaming intake form. Within 1 business day a U.S.-based partner manager replies with a mutual NDA template and a calendar slot—never agency-facing.
What do we receive under NDA?
Full RFP-decode packs, compliance matrices, technical volumes, submission runbooks, and named-resume options scoped to your vehicle and timeline. Prime name, pricing, and agency data stay inside the prime boundary.
Does Techtiz contact the procuring agency?
No. Techtiz is subcontract-only and never faces the agency. Your program manager holds the client relationship, sign-off, and all agency communication.