The words behind tenders, raises
and the knowledge layer.

Agent access

The third part of the knowledge layer: permissioned context for models and agents through an API and an MCP server. A key acts as its owner, with that person's access and nothing more, and any change an agent wants to make arrives as a proposal a person approves in the review queue. See agent access.

Attribute

A field on a CRM object: text, number, currency, date, select, and so on. Ishara's attributes include server-computed formula fields, and every attribute filters, sorts, and exports like a normal column rather than living only on the record page.

Award

The decision that closes a tender: the buyer names the winning bid, and many portals publish the awarded value alongside it. The award date starts the contract clock, which is exactly what recompete tracking watches. Awarded value and final contract value can diverge; see variation order.

Bid bond

A guarantee, usually from a bank or insurer, submitted with a bid to assure the buyer that the bidder will stand behind its offer and sign if it wins. Withdraw after submitting and the bond is forfeited. Amounts and conditions vary by country and by tender, so the conditions published with each tender are the only reliable source.

Bid table

The published record of who bid on a tender and at what price. A bid table lists every bidder, its CR number, its bid amount, the awarded value, and the local-content ratio. Read well, one table tells you who competes in your space and how they price; there is a whole lesson on it in reading a bid table.

Buyer

The government entity running a tender: a ministry, authority, municipality, or state-owned company. Buyers differ in award pace, sector mix, and the suppliers they repeatedly work with, so experienced bid teams profile buyers, not just individual tenders.

Cheque size

The amount an investor typically puts into a single deal, usually quoted as a range. Matching on containment beats matching on overlap: if you are raising a $500k allocation, an investor writing $250k to $2m cheques fits, and one writing $5m to $20m does not, however friendly the meeting. Cheque size is the fastest filter in a raise; see containment.

Containment

The cheque-size filter rule: an investor is kept only when your cheque sits inside the range the investor declares, not merely near it. With a $500k cheque, a $250k to $1m range is kept and a $1m to $5m range is dropped. The investor directory filters by containment, with preset cheque sizes on the facet rail.

Context API

The part of Ishara's API that hands a model the business context behind a task: the people and companies involved, the relationship history, open follow-ups and the brief before a meeting. Each call is logged with its purpose and scoped by the caller's access rules. See developers.

CR number

Commercial registration number: the identifier a company receives when it registers with a state's commercial registry. On a bid table it pins each bid to a specific legal entity, which is how the same supplier can be tracked across tenders even when its name is transliterated differently in Arabic and English.

Deal flow

The stream of raw opportunities entering a pipeline. Investors use the word for companies to evaluate; bid teams use it, or should, for tenders worth considering. Volume is easy to inflate, so the useful measure is how much of the flow actually fits what you can win.

Fit score

A ranking of how well an investor matches a specific raise: sectors, stages, cheque size, geography, recency and lead behaviour against your round. Ishara weighs these openly, and a cheque range that excludes your ask scores zero, never a penalty. A fit score you cannot interrogate is a horoscope; in investor matching, every ranked investor carries an explicit reason for its position.

Follow-on

A further investment by an existing investor in a later round. Funds that reserve capital for follow-ons are signalling a longer commitment, which matters when choosing between two otherwise similar offers. Ask every prospective lead how they think about follow-on reserves.

Formula field

An attribute computed on the server from other fields, for example weighted value = value x probability / 100, or the margin on a bid from its price and cost. Because it is computed server-side, a formula field filters, sorts, and exports like any stored value instead of existing only in the interface.

Framework agreement

A long-running agreement that fixes terms (prices, specifications, conditions) under which a buyer places repeated orders, often called call-offs, without running a full tender each time. Winning one is usually worth more than its headline value suggests; losing one means waiting years for the recompete.

Incumbent

The supplier currently delivering a contract. Incumbents rebid with the advantage of a delivery record the buyer already knows, so challengers who first appear at tender publication are already late. The recompete timing lesson covers when to start instead.

Knowledge layer

The layer between your systems and the people, models and agents that act on them, where context is kept, resolved and served. Ishara's has three parts: public intelligence on the market, private enterprise context from your own work, and agent access for the AI that uses both. A model is only as useful as the context it is given; the layer is where that context lives.

Lead investor

The investor who prices and anchors a round: negotiates the terms, writes the largest or first cheque, and often takes a board seat. Most other investors commit only after a credible lead does, which is why finding the lead is the raise. See follow-on.

Lifecycle (of a tender)

The ordered milestones a government tender passes through, from publication to the end of the contract it produces. Ishara draws five of them on every tender profile as a stepper: Announced, Closing, Technical opening, Financial opening, Awarded, with the contract end beyond the award and any cancellation branching off the line.

1. Announced
2. Closing
3. Technical opening
4. Financial opening
5. Awarded
6. Contract end
7. Cancelled

See technical and financial opening and award.

List

A saved collection of CRM records used for a campaign or a shortlist. Ishara lists carry list-scoped attributes, so the same firm can hold a different status, owner, and note in your raise shortlist than it does in your partnerships list, without the two overwriting each other.

Local-content ratio

The share of a contract's value delivered through the local economy: local staff, local suppliers, local manufacturing. Several states run local-content programmes under their own names and rules, and portals often publish each bidder's ratio in the bid table, where it can affect evaluation scoring as well as price.

MCP

Model Context Protocol: an open standard that lets AI assistants and coding tools call outside tools and read outside data. Ishara runs an MCP server, so an MCP-compatible assistant can look up a person, a company or a meeting brief in your workspace, and propose changes that wait for your approval. See agent access.

Object

In an object CRM, a type of record. Companies, People, and Deals ship ready-made in Ishara; custom objects (tenders, vessels, clinics, whatever your business actually runs on) get the same tables, kanban boards, and record pages. Every CRM term in this glossary hangs off objects.

Pipeline

A staged funnel that moves deals from first contact to a won or lost outcome. The same mechanics fit a raise (contacted, meeting, partner review, term sheet) and a bid funnel (qualify, pursue, submit, award). Both calculators on this site work backwards through pipeline stages from a target: the raise pipeline calculator and the bid pipeline calculator.

Pre-qualification

A screening stage run before or apart from a tender, in which the buyer vets suppliers for capability, financial standing, and registration. Only pre-qualified suppliers may bid, so a missed pre-qualification window can shut you out of work you were otherwise well placed to win.

Private enterprise context

What your own team knows: email, meetings and calls, WhatsApp Business conversations, files and CRM records, resolved into people, decisions and next steps on the right record. It stays separate from public intelligence, follows each conversation's own access rules, and is supplied to a model only at the moment of a request, never used to train models. See private context.

Public intelligence

What is knowable about the market from outside any one company: people and their positions, companies, investors, government tenders and awards, and the signals that say something changed. In Ishara it covers 1.2B people profiles and positions and 17M companies across 140+ authorised data sources, with government tenders across six markets, all inside the same records as your work. See public intelligence.

Ranked list

An ordered list of records, such as the Top-100 style lists in an investor directory. A seat on a credible ranked list is worth noting on a profile as a signal of standing; the exact rank usually matters less than who else appears on the same list.

Recompete

The re-tendering of work when an existing contract expires. Recompetes are the most predictable events in any government tender market, because the expiry date is known long in advance and the incumbent is known too. Ishara's Recompete Radar lists the contracts ending inside your horizon, with the incumbent and the days to expiry.

Recompete horizon

How far ahead a recompete radar looks. In the recompete radar the horizon is a filter you set: a contract appears from the day its end date falls inside it, and is flagged as the date comes close.

Recompete radar

Ishara's list of awarded contracts whose end date falls inside the horizon you choose, each with the incumbent named and the days counted down, so positioning starts months before the RFP. See recompete radar.

Review queue

The human gate between machine-written suggestions and your records. In Ishara, AI output and enrichment suggestions land in a review queue where a person accepts or rejects each change, so AI writes nothing to a record until you approve it. An admin can switch a field to apply automatically, and every such value stays tagged AI. The queue is what makes AI fields auditable instead of merely convenient.

RFP

Request for proposals: a solicitation in which the buyer describes a need and asks suppliers to propose an approach and a price, rather than bidding against a fixed specification. Portals across the region mix RFP, RFQ, ITT, and tender terminology; on this site, tender covers the whole family.

Saved view

A stored configuration of a table or kanban board: filters, columns, sort, grouping. Ishara saved views take nested filters and can be private, shared or workspace-wide, so the pipeline everyone looks at is one URL rather than a screenshot in a chat thread.

Sequence

A scheduled series of emails sent one step at a time until the recipient responds. A sequence that keeps mailing after a reply reads as a robot; in Ishara a reply, a bounce or a suppressed address stops it. A sequence also respects suppression, which is the other half of not annoying people.

Signal

A change in the market that opens a conversation: a job change or promotion, a raise announced, a new investor, a tender published, won or lost, a contract about to end. Ishara attaches signals to the people and companies you track and puts the warm path beside each one. Ishara is the Arabic word for signal. See signals.

Single-bidder award

A tender that attracted exactly one bid and was awarded to it. A cluster of single-bidder awards at one buyer can mean a highly specialised market or simply thin competition; either way it marks the tenders where a capable challenger faces the least resistance. Bid tables are what make these visible.

Supplier

A company that bids for and delivers government work. Studying suppliers, their wins, the buyers they serve, and who they co-bid with tells you who you will meet in the next bid table before it is published.

Suppression

A do-not-email record that blocks sending to an address. Done properly, suppression is scoped by reason: someone who opted out of marketing has not opted out of transactional mail such as an invoice or a signing link. Ishara's email records opt-outs on every send and enforces them on automated sends, scoped by reason, so a newsletter opt-out never blocks an operational message.

Technical and financial opening

The two-envelope procedure many government tenders use: technical proposals are opened and scored first, and financial envelopes are opened later, often only for the bids that passed the technical bar. This is why a bid table sometimes lists more bidders than prices: the losing financial envelopes were never opened.

Tender

A public invitation from a government buyer to bid for a contract, published with a specification, a deadline, and conditions. In Qatar, Bahrain, Saudi Arabia, Kuwait, Oman and the UAE, tenders appear on national procurement portals, each with its own process and vocabulary. The How Government Tenders Work lesson walks through the full lifecycle from publication to award.

Thesis

An investor's stated view of where returns will come from: stages, sectors, geographies, cheque sizes, sometimes one specific conviction. Raises that fit the thesis get read; raises that do not are politely deleted. Matching against thesis is the whole argument for a ranked shortlist over mass email.

Variation order

A formal change to a contract's scope, price, or schedule after award. Variation orders mean a contract's final value can differ substantially from the value in the bid table, in either direction, which is worth remembering when sizing an incumbent's real revenue from a win.

Warm intro

An introduction to an investor through someone they already trust: a portfolio founder, a co-investor, a former colleague. Cold email works occasionally; warm intros work often enough that mapping who can introduce you is worth doing before writing to anyone. Ishara computes warm paths from your own CRM: colleagues, your peer graph, records at the firm's domain, and portfolio companies you already know; see warm path.

Warm path

A route from your own CRM to an investor that Ishara computes for you, as opposed to a warm intro you go and ask for. Four rules produce them: colleagues at the firm, your peer graph, records at the firm's domain, and portfolio companies already in your CRM. The warm introductions use case walks through them.