How much does SIGNLD cost: How It Works in SIGNLD

SIGNLD pricing scales along two dimensions: monthly credits and the number of Topics your team runs. Plans start with a free tier for testing a single connection and question, and move up through paid tiers to Enterprise for organizations running many Topics across departments.

What determines a SIGNLD tier

Two numbers set your tier: monthly credits and the number of active Topics allowed on the account. Credits govern how much question-and-answer activity your team can run in a month. Topics govern how many distinct decision areas, such as cash collection or job margin, stay live at once.

For the wider context, see our overview of what SIGNLD is.

Higher tiers raise both ceilings. A company running one Topic with occasional questions fits a lower tier. A company running Topics across finance, operations, and sales at the same time needs a higher one.

Tier selection is not tied to company size or headcount directly. A ten-person company running five active Topics with daily questions can sit in a higher tier than a fifty-person company that only checks one Topic weekly.

What is a credit spent on

A credit is spent each time SIGNLD processes a question and returns a Decision Brief. Building the initial Knowledge Graph connection to a source system does not consume credits on an ongoing basis. Re-asking a question with fresh data, adjusting a Topic, or exploring the underlying evidence behind a brief draws from the same monthly credit pool.

Teams that ask a handful of questions a week use fewer credits than teams that treat SIGNLD as a daily operating tool across several departments. Credit usage tracks how often people actually use the platform, not how many systems it is connected to.

Credits are not consumed by viewing a previously generated Decision Brief again, sharing it with a colleague, or reviewing the source records linked to it. The credit charge applies at the point a new question triggers a new brief.

What pushes a team into a higher tier

Three patterns typically push a team past a lower tier's limits. The first is adding Topics faster than the tier allows, for example moving from tracking one decision area to five. The second is a jump in daily active use, where more people across the company start asking questions instead of one analyst.

The third is connecting additional source systems that feed new Topics. Since SIGNLD resolves the same customer, job, or invoice across every connected system, adding systems tends to accompany adding Topics rather than happening on its own. Any of these three signals is a reason to review the current tier against actual usage on /pricing.

A fourth, less common pattern is seasonal spikes in question volume, such as month-end close or year-end reviews, where credit usage briefly climbs well above the typical monthly pace. Reviewing usage after a spike helps decide whether a permanent tier change is warranted or the spike was one-time.

What stays the same across every tier

Every SIGNLD tier, from free to Enterprise, includes the same security and architecture guarantees. Connections to source systems are read-only at every tier, with no write-back capability at all. AI inference runs on a single-tenant AWS Bedrock instance regardless of plan size, so no tier shares model infrastructure with other customers.

Source traceability is also constant across tiers. Every Decision Brief links back to the specific records and systems it drew from, so a free-tier user and an Enterprise user get the same evidence trail behind every answer. Tier level changes capacity and scale, not the underlying trust model.

The structure of a Decision Brief itself, a finding paired with supporting evidence, a confidence signal, and a recommended action, does not change by tier either. A free-tier answer and an Enterprise answer are built from the same components.

How do Topics relate to cost

A Topic is the in-app unit for a standing decision area, sometimes called a Decision Topic, such as "which customers are at risk of late payment" or "which jobs are running over budget." Each Topic stays live and answerable, and the number of Topics a plan allows is one of the two pricing levers.

Adding a Topic does not require a modelling phase or new data engineering work, since the Knowledge Graph already resolves entities across connected systems. The cost of adding a Topic is mainly a tier decision, not a setup cost.

Teams commonly start with one Topic per department, such as accounts receivable in finance or job margin in operations, then add more Topics as the first ones prove useful. Each additional Topic draws on the same connected systems already in the Knowledge Graph.

Can a team start small and grow

Yes. The free tier is built for testing a single connection and a single question before committing further. Teams typically start there, connect one system as described in /how-it-works, and confirm the first Decision Brief answers a real question accurately.

From there, moving to a paid tier is a matter of adding Topics or credits as usage grows, not re-implementing the connection or rebuilding a data model. The underlying Knowledge Graph and security architecture do not change when a team upgrades.

How does Enterprise differ from mid-tier plans

Enterprise sits at the top of the tier structure and is built for organizations running many Topics across multiple departments with high, steady question volume. Enterprise plans typically include the highest Topic ceilings and credit allotments in the pricing structure.

Enterprise accounts also tend to connect a larger number of source systems, since SIGNLD supports over 800 systems and larger organizations often run more of their operations across separate platforms. The read-only connection model and single-tenant inference apply the same way at Enterprise as at every other tier.

How should a team budget for SIGNLD

Budgeting starts with counting the decision areas a team wants answered on an ongoing basis, since each one becomes a Topic. From there, estimate how often people would realistically ask questions against those Topics in a typical month to size the credit pool needed.

Teams that overestimate Topic count but underestimate question frequency, or the reverse, often end up on the wrong tier. Starting on the free tier with one real Topic gives a concrete usage pattern to budget the next tier against, rather than guessing in advance.

Where to find current pricing

Dollar figures and per-seat numbers change over time, so this article intentionally does not list them. Current tier pricing, credit allotments, and Topic limits are maintained on /pricing, which reflects the live plan structure at any given time.

Key takeaways

Two numbers set your tier: monthly credits and the number of active Topics allowed on the account.
Every SIGNLD tier, from free to Enterprise, includes the same security and architecture guarantees.
Dollar figures and per-seat numbers change over time, so this article intentionally does not list them.
Usage patterns and overage handling depend on the specific tier and are documented on /pricing.
Connect a system and get a Decision Brief in minutes to see how tiers map to real usage.

FAQ

Does SIGNLD charge per seat

SIGNLD pricing scales on monthly credits and number of Topics rather than a strict per-seat count. Check /pricing for the current structure, since seat-based add-ons can vary by tier.

What happens if a team runs out of credits mid-month

Usage patterns and overage handling depend on the specific tier and are documented on /pricing. The credit model itself, one credit per processed question, stays consistent across all tiers.

Is there a free tier

Yes, SIGNLD offers a free tier intended for testing a single connection and a single Topic before committing to a paid plan.

Does a higher tier get better security

No. AES-256 encryption at rest, TLS 1.2+ in transit, read-only connections, and single-tenant AWS Bedrock inference apply identically at every tier, including free.

Do I need a data team to justify a paid tier

No. SIGNLD is built for companies without a dedicated data team. Tier decisions are based on how many Topics and how much question volume a team needs, not technical headcount.

Can a team downgrade a tier later

Tier changes, including moving to a lower tier, are handled through the account settings tied to the plan documented on /pricing. Topics and connections carry over across tier changes.

Does connecting more systems automatically raise the price

No. Pricing is set by monthly credits and Topic count, not the number of connected systems. A team can connect additional systems to support an existing Topic without changing tier on its own.

Related reading in this series: How SIGNLD cites its sources and Is SIGNLD secure.

Try SIGNLD free

Connect a system and get a Decision Brief in minutes to see how tiers map to real usage. Try SIGNLD free or read /how-it-works first.

How much does SIGNLD cost

In this article