Selling IT and Software to Government: Proof of Concept, Warranty, SLA

From reverse auctions for laptops to management-software contracts: how specification requirements work, what the dreaded proof of concept involves, what on-site warranty means, and what changes when the contract is for continuing technology services.

Published Aug 25, 2026 · Updated Oct 23, 2026 · Busca Licitações Team · 11 min read

This text was written for companies registered in Brazil. Foreign suppliers should also read how foreign companies can bid in Brazilian public tenders.

Technology is one of the sectors that drives the most public procurement, and one of the few where the barrier to entry is not price but the ability to prove that your solution works. City governments replace their computer fleets, state and municipal departments license management systems, hospitals digitize patient records, and city councils hire vendors for their transparency portals.

These are three very different markets, each with its own rules: equipment, software and continuing services. Companies that understand the difference choose where to compete and avoid bidding on tender notices (editais) they could never actually deliver.

Path 1 — Computer equipment

This is the most accessible market and the most contested one. Desktops, laptops, printers, servers, switches, UPS units, projectors and peripherals are bought by virtually every government agency, almost always through an electronic reverse auction (pregão eletrônico) with bidding by item or by lot.

What defines this market is the detailed technical specification. The tender notice describes the processor with a minimum performance score measured against a public benchmark, plus memory, storage, display, ports, energy-efficiency certifications and warranty. Offering a model that fails to meet a single item on that list means certain disqualification.

Two precautions prevent most problems. First, prove the specification: many tender notices require a link to or a catalog from the manufacturer showing that the model offered meets the requirements — a self-declaration is not enough. Second, check that the model is still in production: if a product is discontinued between the bid and the delivery, that is your problem, not the agency's.

The on-site warranty is the other critical point. Tender notices typically require 12 to 60 months of on-site service within a set response time. That means having — or contracting — an authorized service provider able to serve that municipality. Selling to a distant city without a service structure in place means taking a guaranteed loss on the first service call.

Path 2 — Software and management systems

Here the game is different. City governments license or rent systems for public-sector accounting, payroll, tax administration, document tracking, health, education, asset management and transparency. These are continuing contracts of significant value and long duration — and competition is lighter, because they require a ready-made product and the capacity to implement it.

What usually counts more than price:

Proof of concept. After the bidding phase, the top-ranked bidder is called to demonstrate the system before a committee, item by item against the terms of reference (termo de referência). Each requirement is checked live, and failing essential requirements leads to disqualification — even with the lowest price. This is the stage that weeds out the most companies offering a product that does not exist or is incomplete.

Data migration. The agency already has years of information in its current system, often supplied by a competitor. The tender notice usually requires a complete migration on a short deadline, and this is the most labor-intensive part of the implementation. Underestimating it is the classic mistake.

Training and support. Training for civil servants and support with defined service levels, including response and resolution times by severity.

Compliance with financial reporting rules. Public-sector accounting systems must generate the files required by the state audit court (tribunal de contas), in a specific layout and on its own schedule. A system that cannot produce a file the audit court accepts is useless to the city government, no matter how good the rest of it is.

Path 3 — Continuing IT services

Equipment maintenance, managed print services, internet links, structured cabling, hosting, on-site technical support. These contracts are performed month by month, with performance measurement and an SLA.

Local companies have a structural advantage here: when the tender notice requires on-site service within a short time frame, whoever is in the city wins. On the other hand, contracts that involve assigning staff fall under the logic of the cost breakdown spreadsheet (planilha de custos), with all the requirements regarding payroll charges and collective bargaining agreements.

Catalogs, equivalence and the specification fight

One recurring issue in equipment reverse auctions deserves its own section: the debate over equivalence. The tender notice describes one item, you offer another that you consider equivalent or superior, and the committee has to decide whether to accept it.

The practical rule that saves a lot of friction: superior is not the same as equivalent. If the tender notice asks for a specific video port because the existing monitors use that connector, offering a model with a more modern connector means offering something that does not work for them, even if it is better on paper. The specification often carries an unwritten compatibility reason.

That is why, when there is doubt about equivalence, the way to go is a request for clarification (pedido de esclarecimento) before the session, not betting on acceptance. Ask objectively: "Does item 5 allow a model with feature X instead of Y?" The answer becomes part of the tender notice and applies to everyone — which also protects you against a challenge (impugnação) from a competitor later on.

Technical qualification in IT

The technical capacity certificates (atestados de capacidade técnica) required often go beyond quantity and address complexity: number of users served, modules implemented, volume of data migrated, integration with specific systems, availability maintained. A company that implemented its system in a municipality of 5,000 residents may not be able to prove it is capable of doing so in one with 200,000.

That is why growth in IT tends to happen in steps: small municipalities first, then mid-sized ones, then state capitals. Each successful implementation becomes the certificate that unlocks the next tier — a topic covered in how to obtain and use technical capacity certificates.

Restrictive specifications: where to challenge

IT tender notices are fertile ground for steering toward a particular vendor, often unintentionally: the technical team describes the system it already knows. Warning signs that can usually be challenged:

• a set of features that only one product on the market has, with no functional justification;
• a requirement for a specific technology (programming language, database) unrelated to the expected outcome;
• a certificate requiring implementation in a municipality much larger than the contracting one;
• an implementation deadline that makes migrating the described data volume unfeasible;
• a requirement for manufacturer certification that has no bearing on the subject of the contract.

The yardstick is the same as always: a requirement must be necessary and proportionate. Requirements should describe what the system does, not how it is built. See how to challenge a tender notice.

Data protection and security: requirements that have grown

Technology contracts now include personal data protection clauses, and that has raised the bar. Health, education and social assistance systems process sensitive data, and the agency is jointly liable for the processing carried out by the supplier.

What shows up in tender notices: a definition of roles (who is the controller and who is the processor), an obligation to adopt technical security measures, a requirement to report incidents within a short time frame, rules on subcontracting and, at the end of the contract, an obligation to return or delete the data.

For the supplier, three practical steps. First, know where the data is hosted and under which jurisdiction — clauses on data location are increasingly common. Second, have a documented backup policy and recovery plan, because they are frequently required. Third, define who is responsible for incidents and how they will be reported: finding that out in the middle of a crisis is the worst possible time.

Innovation procurement and solutions that do not exist yet

Law 14,133/2021 (Brazil's Public Procurement Law) introduced the competitive dialogue (diálogo competitivo), a procurement method designed precisely for situations where the government knows the problem but does not know what solution is available on the market. Instead of specifying everything up front, the agency holds a dialogue with pre-selected bidders to build the solution, and only then receives bids.

It is still a little-used method, reserved for technological innovation or highly complex contracts, but it is worth knowing: for companies with a differentiated product, it is the format that gives technical differentiation the most room — unlike the reverse auction, where everything comes down to meeting the specification at the lowest price.

There are also instruments to foster innovation outside the logic of traditional tenders, with their own rules. Technology-based companies working in research and development should follow those calls separately — the competition logic and the evaluation criteria are quite different.

Pricing in technology

Beyond the general methodology, there are three specific points. In equipment, exchange rate fluctuations and manufacturer availability are the main risk — demand quotes with a validity period and factor in the real delivery time, which can be long for imported goods. In software, the cost of implementation and migration is usually concentrated at the start, while revenue is spread over the months; plan your cash flow accordingly. In services, the cost breakdown spreadsheet rules apply.

Also factor in the cost of the warranty: 60 months of on-site service in a distant municipality has a cost that must be built into the bid, even if the outlay comes later.

The equipment replacement cycle

Government equipment has both an accounting and a practical useful life, and replacement usually follows a predictable cycle of four to six years. This means that a city government that bought 300 computers in a given year will buy again within a reasonably predictable window — valuable information for anyone who plans ahead.

Add to that the cycles tied to funding transfers: congressional budget amendments, federal agreements to computerize health and education, state modernization programs. A large share of major municipal IT purchases stems from a specific transfer, which explains the tight execution deadlines — the money has a date by which it must be spent.

How to use this: track the procurement history of agencies in your region on each agency page and find out when their last significant purchase in your line of business took place. Anticipating the next window lets you prepare quotes, inventory and technical support in advance, instead of scrambling when the tender notice comes out.

Watch out for extended warranties

This is a detail that tends to eat into margins quietly. When the tender notice requires a 60-month on-site warranty, you are taking on a commitment that spans five years — a period in which the manufacturer may discontinue the model, your authorized service network may change and travel costs will certainly go up.

There are three ways to deal with this in your pricing. The first is to buy the manufacturer's own extended warranty and pass on the cost, which is the safest option. The second is to set aside internally a percentage of the equipment's value for future service calls, based on the defect history of your portfolio. The third, less advisable, is to take on the risk without any provision — common among newcomers and responsible for a good share of IT contracts that start losing money in the third year.

It is also worth reading carefully what the warranty covers. Replacing a part is one thing; replacing the entire unit within a short time frame, with a backup unit while the repair is under way, is another, and a much more expensive one.

Frequently asked questions

Do I need to be a manufacturer to sell equipment?

No. Resellers and integrators account for most deliveries. What is required is proof that the product meets the specification and a guarantee of technical support.

How does the proof of concept work?

The committee schedules a session, with a script based on the terms of reference, and checks the requirements live — in person or remotely. Bring the system in a stable environment, with sample data, and a team that knows every module inside out.

Can open-source software be offered?

Yes, as long as it meets the requirements and the support conditions set out. Many agencies value it, but what decides is compliance with the terms of reference.

Can I subcontract the technical support?

Generally yes, when the tender notice does not prohibit it — but the contractual responsibility remains yours. Put the same deadlines you committed to with the agency in writing with your partner.

Is it worth bidding for a system contract without a ready-made product?

No. The proof of concept exists precisely to eliminate those who promise to develop later. Failing at that stage may also lead to a sanction for submitting an unfeasible or fraudulent bid.

Leasing instead of selling: a model that has grown

Many agencies have shifted from buying equipment to leasing it, especially for printing and, increasingly, for workstations. For the government, the advantage is swapping capital investment for a monthly expense, with maintenance and replacement included.

For the supplier, it changes everything. Revenue is spread over years, which requires capital to finance the installed equipment; maintenance becomes your ongoing responsibility rather than a warranty event; and the contract is usually measured by indicators — pages printed, equipment availability, replacement time.

It is an excellent model for companies with a technical support structure and financial staying power, and a terrible one for those without them. Before bidding on a lease, calculate the break-even point: how many months it takes for the contract to pay for the equipment you have tied up, and what happens if the contract is terminated before then.

Where to start

If you work with equipment, start with small reverse auctions in your municipality and region, where on-site warranty is feasible with the structure you already have. Follow the open IT equipment tenders and note the most common specifications — they repeat from one agency to another.

If your business is software, the path is longer and more profitable: start with small municipalities, with simple implementations, and build up your certificates step by step. Follow the software and systems tenders and read two or three complete terms of reference before bidding for the first time — they reveal precisely what the public market expects from a system, and that information is also valuable for developing your product.

technologysoftwareIT