Frequently asked
questions.

No. Free is a standing plan, not a countdown: the core object CRM, one pipeline board, investor directory browsing, record email on Gmail and Outlook, and CSV import. It exists so you can run real work in Ishara before paying anything.

It means the tiers are young and plans may evolve while Ishara is in early access. The prices on this page are the current list: Free at $0, Pro at $12 per seat per month, Business at $39, Enterprise custom. When anything changes, this page changes with it.

Pro is the raise toolkit: unlimited pipelines and custom objects, investor matching with warm paths and prep briefs, sequences with engagement analytics, automations, webhooks, the API, and the Attio and Pipedrive importers. Business includes everything in Pro and adds the government plane: tender intelligence across all six sections, the recompete radar and bid benchmarks, call intelligence, scheduled reports, and compliance rails.

Enterprise is scoped case by case: custom market and data coverage, onboarding and migration help, a security review, and dedicated support. Email support@lisan.com with a sentence on your team and what you need covered, and we will come back with specifics.

Yes. The chunked CSV importer is on every plan, Free included. Pro and above add the one-click Attio workspace import and the Pipedrive sync with user-to-member mapping. The investor directory and the tender corpus are already in the product, so most of the data arrives without you importing anything.

Summarise the record from what the CRM already holds; research on the web, returning an answer with citations; answer a custom prompt per record; and classify the record into one of the options you define. An AI attribute is a normal column on any object, including custom ones, and accepted values are provenance-tagged as AI.

No. Every AI-proposed value goes through the review queue, which shows exactly what accepting will write and the citations behind it. Accepting writes the value with an AI provenance tag; rejecting writes nothing and keeps the rejected candidate as provenance. Enrichment providers can be set to suggest-into-review, which routes their suggestions through the same queue.

Research-mode answers return the web sources they read, and the review queue displays them next to the proposed value so you can open them before deciding. The job that produced an accepted value keeps its citations. Elsewhere the same rule applies in kind: call insights cite the utterance they came from, and match scores carry an explicit reason.

Ishara routes AI work across multiple providers rather than binding to one. Which providers and features are allowed is a workspace policy that admins set once and every AI surface inherits, so governance lives in one place instead of per feature.

Every bar, slice, and cell carries the filter that produced it. Clicking one opens the records behind the number as a live filtered view built on the same saved-view machinery as the rest of the CRM, and that view is a URL you can share. You act on the records directly rather than reconciling an export.

Only if their access grants it. Dashboards run as the viewing user, so the same dashboard honestly shows each person what their permissions allow: a manager sees the team, a rep sees their own book. Scheduled delivery sends dashboards out on the cadence you choose.

Aggregates never silently convert. When a group spans currencies and a rate is missing, the total splits by currency, showing each sum side by side instead of inventing a single blended number. Less tidy, but true, and it applies to group totals across the product, not just analytics.

Yes, both directions. Outbound webhooks deliver record events to URLs you register, inbound webhooks let outside systems post events in to start runs, and API keys are created and revoked inside the app with the docs beside them.

The run lands in a dead-letter queue with its state intact: the trigger, the steps that executed, any waits, and where it stopped. Nothing is silently dropped, and the mail outbox separately flags a stuck queue by checking the age of the oldest queued message against the sender's cadence.

Assignment runs in the database on insert, so it cannot race the UI or depend on an open browser tab. Rules come in three modes: round robin across a pool, fixed owner, and territories matched on country, states, and cities. Read-only counters record how many records each member received and when, as an audit trail.

Yes. You schedule a MeetriX bot into the meeting and it records in Arabic or English, returning a speaker-resolved transcript with playback. Insights generated from the call cite the specific utterance they came from, so an Arabic-language claim is as checkable as an English one.

Visibility is set per interaction. Each call carries its own policy, so a sensitive negotiation can be restricted to the people who were in the room while routine calls stay visible to the team. Calls that land through the org-wide reconcile follow the same policy model.

Not yet. Transcript search and cross-call Q&A are planned, alongside tasks and notes write-back, deal risk signals, auto-join for external meetings, and live captions. Shipped today: bot scheduling in Arabic or English, speaker-resolved transcripts, playback, cited insights, org-wide reconcile, and per-interaction visibility. The roadmap page tracks the rest.

Gmail and Outlook, two-way. Mail you send from Ishara lands in your provider's sent folder, and incoming mail threads onto matching records automatically. Matching runs across every object, so a thread attaches to the person, the company, and the deal it concerns, including custom objects, not just a contact card.

Click tracking runs through branded tracking on your own domain, and marketing sends carry a one-click unsubscribe. Suppression is scoped by reason: a marketing opt-out stops marketing mail and nothing else, so a transactional message like a signature request or an invite still delivers. There is also a blocked-senders list that keeps named addresses out of sync and matching entirely.

The send guard. Every variable can declare a fallback with {{variable|fallback}}; a variable that resolves to nothing and has no fallback blocks the send and names the missing field. Sequences pass the same guard on every step, so a broken merge field cannot ship at step three either.

No. A reply pulls the contact out of the sequence immediately, so no follow-up lands after the conversation has already started. Every sequence step also passes the send guard and the per-reason suppression check before it leaves.

Create an API key in Attio's developer settings with read scopes and paste it into Ishara. A preview counts your records per object, lists, members, notes, and tasks before anything is written, then the import runs in phases, schema first, bringing over members, records, pipelines, lists, notes, tasks, and comments. Custom objects stay custom objects.

No. Every imported record keys on its Attio id, so re-running the import never duplicates. A toggle controls what a re-run does with records that already exist: re-apply the current Attio values, or only add records that are new.

Only if your workspace policy allows it. The chain tries a local directory of roughly 743,000 brands first, free, then Logo.dev, Brandfetch, and Apollo, and each write is governed by policy, including suggest-into-review, where a human accepts or rejects every proposed value. Every stored value is provenance-tagged, so enriched data never masquerades as typed data.

Deletes go to a trash with a retention window rather than disappearing, every bulk delete states the exact record count before you confirm, destructive actions come with undo, and the audit trail records who did what. Dedupe is exact-match and merge-based, so cleanup is provable rather than guessed.

32,822 investors on day one, reachable through five doors: an investors plane, a companies plane with backers drill-down, firm dossiers, ranked lists kept as data, and 1,793 bilingual Saudi ecosystem organisations. 34,097 investor photos are downloaded and self-hosted so profiles do not rot when source links die.

Today, 175 of the 32,822 investors are located in MENA. That gap is real and we publish it. An enrichment pass built around LEAP 2026 is adding 272 investment entities and 572 investor people from the region; it is in progress, not finished, and every value lands provenance-labelled.

You name the cheque you are raising in, and the filter keeps an investor only when that number sits inside their declared cheque range. A naive overlap filter would also return funds whose enormous claimed ranges merely brush yours; containment drops them, so the result is a page of plausible cheque-writers.

The corpus is compiled from public sources and self-declared profiles, and it is labelled rather than laundered: every stored value carries its provenance, self-declared claims never share a column with verified facts, and truncated counts display as 50+ instead of a guessed number.

You describe the raise in four inputs: sectors, stages, locations, and the cheque you are raising in. Ishara ranks the 32,822-investor corpus against that description and attaches the explicit reasons to every name on the shortlist, so you can verify the fit instead of trusting a bare score. The result is a URL you can share with your co-founder.

Warm paths are introduction routes computed with four join rules against your own workspace only: colleagues in your CRM who work at the firm, investors in your book who have co-invested with the target, records at the firm's email domain, and portfolio companies of theirs already in your CRM. Ishara never mines other customers' data to manufacture an intro.

Exactly two ingredients: the corpus facts on that investor's profile and the warm paths from your own workspace. It reads in about a minute and is cached per investor, so reopening it before the meeting is instant. It never guesses beyond those sources.

Multi-select any set of results and push them into a staged raise pipeline in one action. Add-to-CRM is idempotent, so an investor already in your book is never duplicated, and In-CRM badges on the shortlist show who you are already tracking.

Yes. Companies, People, and Deals are seeded records on the same kernel your custom objects use. A custom object gets the same table and kanban screens, saved views, automations, and email matching, with the same 19 attribute types.

A formula field is computed on the server rather than in your browser, so it behaves like stored data: you can filter a saved view by it, sort a table on it, and it comes through in exports. Stored, formula, and relationship are the three attribute modes.

You choose per view: private (only you), shared (people you share it with), or workspace-wide. Both table and kanban layouts work at every scope, and filters support nested and/or/not trees with 13 operators.

Every stored value is tagged with its source: user, import, automation, formula, AI, enrichment, or system. AI-drafted values sit in a review queue until a human accepts them, and enrichment writes follow the policy you set, including suggest-into-review.

Yes. Each pipeline is its own board with its own URL, swimlanes, and bulk actions, and the deals grid shows every deal across all pipelines in one table. A raise funnel and a bid-team funnel can run side by side with different stages.

Drag is optimistic, so your card moves instantly, but the server reconciles every move by row version. If a teammate changed the deal in the meantime, the conflict is detected and resolved against the current row instead of one edit silently overwriting the other.

Whatever you choose to share, on a brandable page gated by a token: the person on the other side follows the link and sees it under your brand, with no login and no account to create. Access is carried by the token in the link itself.

A contract coming back to market. Government work is awarded for a fixed period, and when the period ends the work is usually tendered again. Because the buyer, scope, incumbent, and approximate date are all knowable in advance, a recompete is the most predictable deal in government contracting, and the teams that win them start pursuit from the contract end date, not the RFP date.

Arithmetic on the published record: where a portal publishes an award date and a contract period, the radar computes the end date and counts down to it. Rows carry the incumbent supplier and awarded value, and you filter by horizons from 6 to 24 months, by buyer, sector, or value. Where a portal does not publish the period, no end date is invented.

From real bid tables, the published record of who bid what on past tenders. Ishara computes bidder-count histograms, winner-versus-median spread, and award-value percentiles per category, and every statistic states the sample size it was computed from. Benchmarks exist only where portals publish bid tables: Qatar today, with Bahrain next as its coverage lands.

Yes. Any contract on the radar links back to its award in the tender corpus, where one click opens the buyer and incumbent dossiers and tracks the pursuit into your CRM. From there it runs like any deal: a staged bid pipeline, tasks, email on the record, and automations. A 24-month horizon view is effectively your business-development plan, pre-sorted by deadline.

The coverage model spans six states: Qatar, Bahrain, Saudi Arabia, Kuwait, Oman, and the UAE. Qatar is the only market crawled live end to end today, with full bidder tables and a daily refresh. Bahrain is next, and the remaining four are planned. Each market page states what that state's portals publish and exactly what Ishara covers now.

Arabic and English titles and entities side by side, the buying entity, sector, values, key dates, bond values and documents where published, and a lifecycle timeline across eight statuses from announcement through award. Where the portal publishes a bid table, the profile carries all of it: every bidder, its commercial-registration (CR) number, bid amount, awarded value, and local-content ratio.

A buyer dossier shows a government entity's award trend over time, its sector mix, the suppliers who win with it most, and a competition-health signal based on how many bidders its tenders draw. A supplier dossier shows a company's tender wins, the buyers it serves, its reach across sectors, and a co-bidder teaming graph drawn from real bid tables.

Two ways. Track-in-CRM turns any single tender into a workspace record in one click, with the profile attached. For batches, multi-select tenders in the directory and send the tray into a bid-team funnel, a staged pipeline your pursuit team runs like any other board. Every filtered directory view is also a shareable URL, so qualification starts from the same list for everyone.

No. Qatar is the only tender market crawled live end to end today, refreshed daily. Bahrain is the next market on the roadmap, and this page exists so you know exactly what is coming rather than guessing from a coverage map.

Opened-bid prices, made public when bids are opened, and a monthly award archive reaching back to 2016 with the winner and awarded value per authority. That published record is why Bahrain is the next market rather than one of the planned ones.

Yes, once live. Ishara computes bid statistics only where portals publish the underlying bid data, which is why benchmarks exist for Qatar today. Bahrain's opened-bid prices meet the same bar, so it joins the benchmarks plane when coverage lands, with sample sizes shown honestly.

No. Kuwait is a planned market. Qatar is the only tender market crawled live end to end today, refreshed daily. Kuwait's planned entry point is the energy-sector procurement portals, with broader CAPT-centred coverage as access opens; the roadmap tracks progress.

Kuwait publishes per-ministry budgets with capital and operating detail every month. That cadence lets you watch a ministry's spending capacity move before tenders appear. Ishara's Budgets plane shows budget lines with a per-state coverage note, so it will state plainly when Kuwait lines are loaded, and never pretend before then.

The full CRM and the investor plane: 32,822 investors with explained matching and warm intro paths, pipelines, record email with templates ranked by real reply rates, automations, and analytics. Teams bidding regionally also get Qatar's live tender coverage with full bidder tables.

No. Oman is a planned market. Qatar is the only tender market crawled live end to end today, refreshed daily, and Bahrain is next. Oman's plan starts from the aggregate dashboards the Tender Board publishes; the roadmap tracks progress.

It means Ishara will present the totals and trends the Tender Board actually publishes, with a coverage note stating what sits behind them. Row-level tender detail and bid statistics are added only when Oman publishes them; nothing is inferred or invented in the meantime.

From Monaqasat, Qatar's government procurement portal, crawled end to end and refreshed daily. Titles and entity names are carried in Arabic and English as published, and every tender is tracked across eight lifecycle statuses from announcement through award.

Where the portal publishes results, Ishara shows the full bidder table: every bidder with its commercial-registration number, bid amount, awarded value, and local-content ratio. Losing bids are half the intelligence; they are what make competitor dossiers and pricing benchmarks possible.

Because benchmarks are computed from published bids, and Qatar's portal publishes full bidder tables. Ishara only shows bid statistics where the underlying bid data is public, with the sample size stated next to the number. Bahrain publishes opened-bid prices and joins the benchmarks plane when its coverage goes live; Saudi Arabia, Kuwait, Oman, and the UAE are planned.

Yes. Track any tender as a CRM record in one click, or multi-select a set of tenders into a bid-team funnel, then run pursuit with the same pipelines, record email, approvals, and analytics as any other deal in Ishara.

No. Saudi Arabia is a planned market. Qatar is the only tender market crawled live end to end today, refreshed daily, and Bahrain is next. Saudi coverage is planned through Etimad's official access programme, and the roadmap page tracks progress.

Because Saudi procurement runs through one platform, the durable route in is the official one. An approved integration gives stable coverage of the region's largest procurement market, which is worth more than a fragile shortcut that breaks without notice.

The Saudi ecosystem directory is live: 1,793 organisations with Arabic and English names inside the investor plane. So are the 32,822-investor directory, explained matching with warm intro paths, and the full CRM: pipelines, record email, automations, and analytics. Teams bidding regionally also get Qatar's live tender coverage today.

No. The UAE is a planned market. Qatar is the only tender market crawled live end to end today, refreshed daily, and Bahrain is next. UAE federal procurement runs through the Federal Digital Procurement Platform, where public browsing is login-gated, so coverage is planned as access allows.

Because honest coverage follows access. With no openly browsable federal tender archive, Ishara does not pretend to coverage it cannot deliver. Each market page states exactly what is covered now, and the roadmap shows what is planned; when UAE access opens, this page will say precisely what is included.

The investor plane and the CRM in full: 32,822 investors with explained matching, warm intro paths, and grounded prep briefs, plus pipelines, record email, automations, analytics, and one-click migration from Attio or Pipedrive. Teams bidding regionally also get Qatar's live tender coverage today.

That is the case it is built for. Both are flexible-object CRMs with custom objects, saved views, and lists, so the kernel will feel familiar. Ishara adds what an empty CRM cannot: a 32,822-investor directory, government tender intelligence with Qatar live and refreshed daily, a bilingual Arabic and English data model, and call bots that work in Arabic. Attio remains the more polished product with the larger ecosystem, and if your data is global and self-supplied that may decide it.

Yes. Create an Attio access token, paste it into Ishara, and the whole-workspace import runs in one click. Be aware the importer goes one way: Ishara does not write a workspace back into Attio, so keep your Attio export and reconcile record counts before archiving anything.

As of September 2026, based on public pages: the market data planes (an investor directory of 32,822 profiles and a government tender corpus with full bidder tables where portals publish them), investor matching with an explicit reason per ranking plus warm paths from your own CRM, a bilingual Arabic and English data model, Arabic call intelligence, and AI whose writes are gated by a human review queue. Attio wins on polish, speed, and ecosystem momentum, and we say so plainly.

No. Ishara covers one-to-one selling and raising: tracked email, templates, sequences, engagement analytics, and per-reason suppression, but no landing pages, ads, or blog tooling. If full marketing automation decides your purchase, HubSpot wins that point as of September 2026.

Ishara uses per-seat early-access plans: Free, Pro at $12 per seat per month, Business at $39 per seat per month, and Enterprise custom, with the caveat that plans may evolve. We will not quote HubSpot's prices; its public pricing is organized around hubs and tiers as of September 2026, so model your exact stack on its current pricing page before comparing.

Not that its public pages describe as of September 2026. Ishara ships a directory of 32,822 investors with fit-scored matching, plus government tender intelligence with Qatar live today and full bidder tables where portals publish them. Verify current HubSpot offerings directly before deciding.

Not that its public pages describe as of September 2026; Pipedrive is a general-purpose sales CRM and you bring your own lists. Ishara ships a directory of 32,822 investors with fit-scored matching, a stated reason for every ranking, and warm paths from your own CRM. Verify current Pipedrive add-ons directly before deciding.

Yes. Ishara ships a Pipedrive sync with member mapping so records land with the right owners, plus chunked CSV import for anything else, with exact-match duplicate merge. Every imported value carries a provenance tag, and destructive actions have count-and-confirm, undo, and a full audit trail. Reconcile open deals before retiring the old account.

No. Ishara runs on the web and in the Lisan desktop app; there is no dedicated mobile app today, while Pipedrive ships mature iOS and Android apps. If phone-first CRM work decides your purchase, Pipedrive wins that point as of September 2026.

When one person works a pipeline that fits on one screen, you already know everyone on the list, you bid on one portal that genuinely gets checked daily, and nobody else depends on the sheet being current. Plenty of early teams pass that test. It fails the moment the list needs discovering, replies need remembering across dozens of threads, or a submission deadline can hide between portal checks.

Yes. The chunked CSV import wizard is built for big files: it maps your columns to typed attributes, and exact-match duplicate merge keeps re-imports clean. If your tracker lives in a CRM instead, there are dedicated Attio and Pipedrive importers. The free early-access tier lets you load the sheet and judge the result before paying anything.

A hand-checked sheet trails the portal by the length of your checking habit. Ishara's coverage model spans Qatar, Bahrain, Saudi Arabia, Kuwait, Oman, and the UAE, with Qatar live today and refreshed daily; Bahrain is next and the rest are planned, which the roadmap states openly. On top of the feed, the recompete radar surfaces awarded contracts approaching expiry before the new tender is ever published, and tender profiles carry full bidder tables where portals publish them.

Coverage is roughly 1 divided by your win rate. At a trailing 25% win rate you need about 4x the revenue target in submitted bid value; at 15%, closer to 7x. Generic sales folklore says 3x, but a bid pipeline should be derived from your own win rate, not defaulted.

Everything the bid consumes: proposal team time, bond and tender document fees, translation, legal review, pricing work, and partner coordination. Teams that only count document fees underestimate badly; a serious government bid usually carries a five-figure loaded cost. The input is optional, but the total is sobering.

They are illustrative planning anchors: a 25% win rate and 5 tenders reviewed per bid submitted. Replace both with your trailing numbers. Where portals publish full bidder tables you can also sanity-check the win rate structurally: 1 divided by the typical bidder count in your category is the base rate before any edge you bring.

Work backwards from the money. Divide your target raise by your average cheque to get cheques needed, then divide by your meeting-to-term-sheet, reply-to-meeting, and reply rates in turn. With illustrative cold-outreach rates (12% reply, 40% reply-to-meeting, 10% meeting-to-term-sheet), a $2M raise at $250k cheques means contacting about 1,700 investors. Warm introductions and a well-targeted list shrink that number dramatically.

No. They are editable illustrative assumptions for cold outreach, and your real rates depend on how warm the path is, how well each investor fits your cheque size and sector, and whether you follow up. Replace them with your own numbers as your raise produces data.

No. All of the math runs in your browser on this page. Nothing you enter is stored, transmitted, or logged.

No. Every planned item comes from a written plan of record, but Ishara does not promise ship dates, and the order can shift with what users need first. When something ships, this page moves it to the shipped column rather than leaving it as a promise.

Ishara pricing is per seat and in early access, so tiers may evolve. Where a new capability lands in the plans is decided when it ships, and the pricing page always carries the current list.

The published record of who bid on a tender and at what price. Where portals publish them in full, a bid table lists every bidder, its CR number, its bid amount, the awarded value, and the local-content ratio.

The share of a contract's value delivered through the local economy: local staff, suppliers, and manufacturing. Several states run local-content programmes under their own names and rules, and some portals publish each bidder's ratio in the bid table.

Qatar is crawled live end to end, with full bidder tables and a daily refresh. Bahrain is next, with opened-bid prices and an award archive. Saudi Arabia, Kuwait, Oman, and the UAE are planned. Each market page states exactly what its portal publishes and what Ishara covers now, so you can judge the fit for your market before you commit.

Where the portal publishes one: every bidder, its commercial-registration number, the bid amount, the awarded value, and the local-content ratio, alongside the tender's lifecycle timeline, bond and document fees, and contract dates. Bid statistics only exist where portals publish these tables, which is why every benchmark panel in Ishara states its sample size.

Yes. Pipelines carry stage-entry requirements, so a bid cannot advance until the fields and steps you define are complete, and approvals snapshot the numbers at ask time, so sign-off is anchored to what was actually asked. Deals hold quotes, line items, files, and comments with mentions. If your process needs its own shapes, custom objects get the same screens, and a chunked CSV import brings your pursuit history in.

Yes, and the kernel is built for it. Model each engagement as a custom object with the same screens the built-in objects get, keep per-client shortlists as lists with list-scoped attributes so scoring columns never leak onto shared records, and scope saved views as private, shared, or workspace-wide so each analyst works their own slice while partners see the practice.

From the region's public procurement portals, compiled into a bilingual corpus with Arabic and English in the data model. Qatar is crawled live end to end today and refreshed daily; Bahrain is next; Saudi Arabia, Kuwait, Oman, and the UAE are planned. Bidder tables appear where portals publish them, benchmark panels state their sample sizes, and every stored value carries a provenance tag.

Three ways. Every filtered view, dossier, and match page is a URL, so a finding is a reproducible link for anyone working in the workspace. Dashboards run as the viewer and deliver on a schedule, with every chart drilling back to its underlying records. And views export, formula columns included, so the appendix table comes from the same filter that made the chart.

You describe the raise: sectors, stages, locations, and cheque size. Ishara filters 32,822 investors by cheque-range containment and fit, then returns a ranked shortlist where every investor carries an explicit reason for its position. The match page is a shareable URL, warm paths mined from your own CRM show who can introduce you, and a multi-select sends the names you choose into a staged raise pipeline without creating duplicates.

Honest answer: the global set is deep, at 32,822 investors with 34,097 self-hosted photos, but only 175 of those investors are located in MENA today, because regional data is thin in every database, not just ours. An enrichment adding 272 regional investment entities and 572 investor people is in progress, and 1,793 bilingual Saudi ecosystem organisations are already in. For cross-border raises the directory is strong now; the regional set grows as the enrichment lands.

Early-access pricing: a Free tier to start, Pro at $12 per seat per month, Business at $39 per seat per month, and custom Enterprise plans. Plans may evolve as early access matures. A raise is usually one or two seats, so the tooling costs less than one flight to a partner meeting.

Ishara is a deal-intelligence CRM: a flexible object CRM fused with two reference-data planes, a directory of 32,822 investors with explained matching and warm intro paths, and a bilingual government tender corpus whose coverage model spans Qatar, Bahrain, Saudi Arabia, Kuwait, Oman, and the UAE, with Qatar live today. AI features cite their sources and route through a human review queue. Ishara is part of the Lisan platform and runs on the web and in the Lisan desktop app.

Ishara (إشارة) is Arabic for signal. The product is built around that idea: surfacing the right investor, the expiring contract, or the reply-worthy template out of the noise of deal-making. The four-point Signal Star in the mark is that pulse.

Qatar is crawled live end to end, with full bidder tables and a daily refresh. Bahrain is next, with opened-bid prices and an award archive reaching back to 2016. Saudi Arabia, Kuwait, Oman, and the UAE are planned; each market page states exactly what its portals publish and what Ishara covers now.

From public sources and self-declared profiles, compiled into a reference corpus. Every value is provenance-labelled: self-declared claims never share a column with verified facts, truncation shows as a count like 50+ rather than a guess, and 34,097 photos are downloaded and self-hosted so they do not rot.

AI in Ishara shows its work. Web research answers carry citations, call insights point at the utterance they came from, and prep briefs are built only from corpus facts plus your own warm paths. Nothing is written to a record until a human accepts it in the review queue.

From Attio, one click imports the whole workspace: schema, records, pipelines, lists, notes, tasks, and comments. From Pipedrive, a sync connector with user-to-member mapping. From anywhere else, a CSV wizard that imports in bounded chunks so big files survive.

Yes. They are captures of the actual product screens, rendered by the same code the app runs, seeded with sample data so no customer information appears. What you see is what ships.

The captures run on small, deterministic sample datasets so they stay honest and reproducible. In the product, the directory carries 32,822 investors and the tender corpus grows with every daily refresh.