Log in

SLED contracting software that sorts your bid feed and puts each bid/no-bid decision on one card

Your bid feed sends more state and local notices than you can read, and you spend evenings in PDFs to learn a bid isn’t yours. Tommo Bids, part of Tommos (tommos.ai), reads your HigherGov search daily and sorts each new bid Ours or Not ours, with one sentence why. Each bid that fits gets a card quoting the contractor’s duties word for word, and you decide: Bid, Bid as a subcontractor or No bid.

Tommo Bids is not part of the Tommos plans. We share its price on the demo call and turn it on for your workspace once you say yes.

One bid, card by card#

The firm, the district and the bid below are made up. The steps are the product’s.

Brightline IT is a 40-person managed services firm in Columbus, Ohio. Its HigherGov saved search covers network and IT support work in Ohio and Indiana. Its NAICS codes in Tommos are 5415 and 5182.

  1. 1

    Monday, the daily read

    A school district posts a request for proposals: managed network services for 14 buildings, three years, proposals due in 24 days. Tommo Bids reads the notice beside Brightline’s two short texts, the work it sells and the work it turns away, and sorts it Ours: “Network support is the main part of what the district buys.” The same read sets aside a county’s bid for body cameras, because its NAICS code is not one of Brightline’s. The county bid waits in the Not ours column, under Not in our codes.

  2. 2

    The deal and its folder

    The district’s bid lands in the New column of the Bids board, and its eight files go into its folder in Brightline’s Drive. From them Tommos pulls out the deadline for questions, a mandatory pre-bid walk-through, how the proposal is sent (the district’s portal, one PDF, 30 pages at most) and the scoring criteria with their weights, each in the file’s words, with the file and section it came from.

  3. 3

    The card

    In Flow, your list of decisions in Tommos, a card asks: “Bid on Managed network services for 14 school buildings?” Its body is one passage from the scope of work, word for word: “The Contractor shall provide on-site network support at each of the District’s fourteen (14) buildings during school hours.” Under Bid details: the due date, the term, what the notice asks of a bidder, and the papers missing from the Bids credentials folder. The card also flags that Brightline’s certificate of insurance expires before the due date. Tommo Bids’ own reasoning sits under Why, apart from the buyer’s words.

  4. 4

    The answer

    Brightline’s owner presses Bid. The record keeps the answer and the name, and the deal moves to Preparing.

  5. 5

    The preparation

    Brightline has turned on the job “Submit the bid”, which is off in a new workspace, so Tommo Bids writes three Google Docs into the bid’s folder: what the district requires, a schedule worked back from the due date with the question deadline and the walk-through, and a first draft of the staffing section. Where the record holds no fact, the draft reads [blank] and names whom to ask. The notice names a contact at the district. Tommo Bids drafts a question to that contact about after-hours support, on a card. The owner edits one line and presses Send.

  6. 6

    The people’s part

    Tommo Bids puts two steps only a person can take into Flow as tasks: get a current certificate of insurance, and submit on the district’s portal.

  7. 7

    Submitted, two days before the due date

    The bid manager uploads the portal’s confirmation and presses Mark submitted. The record keeps the proof, who marked it and when.

After you answer, and what stays with your people#

Bid and Bid as a subcontractor both move the deal to Preparing. Bid as a subcontractor opens no job, and your people take the work from there. No bid asks why, and the bid moves to Not ours under your name and your reason; Restore the deal brings it back with its files. If nobody answers, the card closes once the due date passes, and the deal stays where it stands.

The work after Bid belongs to a job called “Submit the bid”, with its own switch. A new workspace starts with it off: Bid moves the deal to Preparing, and the bid is yours to submit. With the switch on, Tommo Bids writes the list of what the buyer requires, a schedule worked back from the due date and drafts of sections, each as a new Google Doc in the bid’s folder, and changes nothing already there. It also drafts the questions to the buyer during the question period, and the submission email itself when the buyer takes bids by email, once the deal has a person at the buyer to write to.

With the job on, your people keep:

  • Every email to the buyer. Tommo Bids drafts it on a card, and a person presses Send.
  • What only a person can do. Sign a form, get a certificate, register on the buyer’s portal, submit on the portal. Each comes as a task in Flow. Tommo Bids does not log in to a portal.
  • The proof. A person presses Mark submitted with the buyer’s receipt or the portal’s confirmation. Without proof, Mark submitted changes nothing.

A bid you move to Won stays in Tommos as a won deal, and the next bid/no-bid card counts it as past work.

Questions SLED contractors ask#

What is SLED contracting?
State, local and education contracting: selling to states, counties, cities, school districts and utilities. A state, a county or a city buys through its own portal, with its own rules, forms and vendor registration, so a firm that bids in several places either watches many portals or pays for a feed that gathers them. Then someone still reads every notice in it.
Do we have to use Tommos as our CRM?
Yes. Tommo Bids works inside Tommos: each bid that fits becomes a deal on the Bids board, and your won deals there are the past work each bid/no-bid card cites.
Which bid feeds does Tommo Bids read?
HigherGov, through your own account: you build the saved search and make the API key there. A source HigherGov does not cover comes in through a module, a small package a developer writes for that source. Its bids reach the Bids board only after a person tests the module and moves it to Live.
Does Tommo Bids submit bids on its own?
No. It does not log in to a portal, and a person submits on it. With the job "Submit the bid" on, Tommo Bids puts the requirements, the schedule and first drafts in the bid's folder, files each step only a person can take as a task, drafts each email to the buyer for a person to send, and asks a person to press Mark submitted with the proof.
What if the triage sets aside a bid we want?
Open the Not ours column and press Work the bid on it, or drag it to the first column. The triage reads your decision on similar bids after that.
Will the board inflate our pipeline?
No. Until you type your amount, a bid shows an estimate marked ≈. An estimate is a guess about a contract you have not won, so the board counts bids and never adds estimates up. Once you type your own amount on the bid, the card and the bid's page show it in place of the estimate.
Does Tommo Bids read federal bids too?
Yes. You choose a level for each HigherGov saved search you add: Federal or State and Local. A search is read at one level only, so to read both, add the same search twice, once at each level. A bid that both searches find comes in once.
How do we get Tommo Bids?
Tommo Bids is not part of the Tommos plans. We share its price on the demo call and turn it on for your workspace once you say yes.

Know why each new bid is Ours or Not ours

Tommo Bids sorts each new bid from your HigherGov search against your NAICS codes and your own words for the work you sell, and gives one sentence why. Book a demo of Tommo Bids: pick a time on the calendar. If none fits, leave your email in the form, and we'll write back to set the call.

Book a demo

Rather see it first?

Ask through our form, and the answer comes from us.