Softwr

Construction · head to head

Briq vs Height

Briq logo

Briq

Construction

Financial automation and forecasting for contractors sitting on top of construction ERP

From
On request
Rated
-
H

Height

Technology

A project management tool from a small independent vendor that uses AI agents to handle routine ticket maintenance.

From
Free
Rated
-

The short version

  • Only Height has a free tier, so it costs nothing to try first.
  • Each has a real cost: Briq briq layers on top of an ERP rather than replacing it, so the total finance software bill goes up and the business case has to come from headcount or close-time savings that are hard to measure in advance.; Height it is one product from one small venture-funded company with no second line of business underwriting it, so adopting it as your system of record is a bet on that company's funding, and the tool holds work history you would have to reconstruct elsewhere if the bet fails.
  • They diverge on capability: Briq covers Invoice capture and coding, Height covers Autonomous triage.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Briq and Height actually diverge.

Attributes where Briq and Height differ
AttributeBriqHeight
Starting priceOn requestFree
Pricing modelquoteUnknown
Free tierNoYes
CategoryConstructionTechnology
FoundedUnknown2018

Identical on both: platforms (Web), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Briq

  • Invoice capture and coding
  • WIP schedules
  • Cash flow forecasting
  • Cost at completion forecasting
  • Multi-entity consolidation
  • Overhead allocation
  • Workflow automation
  • Dashboards and reporting

Only in Height

  • Autonomous triage
  • Duplicate detection
  • Attribute maintenance
  • Per-task chat
  • Multiple views
  • Developer integrations
  • Custom fields and filters
  • Public API

What people use each for

The jobs each tool is most often brought in to do.

Briq

  • A contractor whose month-end close runs three weeks because WIP is rebuilt by hand in Excel every periodnot Height
  • A group with four operating companies on different chart-of-accounts structures that needs one consolidated margin viewnot Height
  • A specialty contractor processing thousands of supplier invoices a month that wants coding and approval automated rather than keyednot Height
  • A finance director who needs a defensible cost-at-completion forecast for a surety or lender rather than a project manager's estimatenot Height

Height

  • A product or engineering team with no dedicated project manager, where backlog upkeep currently falls on whoever has timenot Briq
  • Teams leaving Jira because its configuration and administration cost more attention than the tracking is worthnot Briq
  • A support or intake queue where incoming requests need categorising and deduplicating before anyone can plan themnot Briq
  • Startups that want tasks, chat and progress tracking in one tool rather than stitching a tracker to a chat appnot Briq

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Briq

  • Briq layers on top of an ERP rather than replacing it, so the total finance software bill goes up and the business case has to come from headcount or close-time savings that are hard to measure in advance.
  • The output is only as good as job cost coding in the underlying ledger, and contractors with inconsistent cost codes get faster visibility of a mess rather than a clean forecast.
  • No pricing is published and the contract is scoped by entities, modules and transaction volume, which makes budgeting impossible without a full discovery exercise.
  • Implementation is a data mapping project against systems such as Vista and Sage 300 that were not designed to be read this way, so go-live timelines run into months and depend on your own finance team's availability.
  • It targets mid-market and larger contractors; a firm with one entity and a competent controller in Excel will not recover the cost, and the product is oversized for smaller subcontractors.

Height

  • It is one product from one small venture-funded company with no second line of business underwriting it, so adopting it as your system of record is a bet on that company's funding, and the tool holds work history you would have to reconstruct elsewhere if the bet fails.
  • The 2024 relaunch as Height 2.0 reoriented the product around AI agents and changed workflows customers had already built on, which is the clearest available evidence of how much the product may be re-shaped again under you.
  • The ecosystem is small next to Jira, Linear and Asana: fewer third-party integrations, no consultancy market, and far less written material to search when something behaves unexpectedly, so support questions go to the vendor and wait.
  • The automation only pays off if tasks contain enough substance for a model to work with; on a team whose tickets are two-word titles, the agents have nothing to triage or deduplicate and the product reduces to an ordinary tracker at a premium.
  • Task content is processed by hosted large language models, so a security review becomes a question about subprocessors and data handling, and there is no self-hosted or on-premises deployment to fall back on if the answer is unacceptable.
  • There is no widely used two-way synchronisation with Jira, so an organisation where one team adopts Height and the rest stay on Jira ends up with two systems of record and manual reconciliation between them.

Pricing, plan by plan

Briq

On request
  • Briq$undefined/year
    • Annual platform subscription
    • Scoped by modules, entities and transaction volume
    • Implementation and data mapping quoted separately

Height

Free

No published plan breakdown. See the Height review.

Which should you pick?

Choose Briq if

  • You need invoice capture and coding.
  • You also want wip schedules.

Choose Height if

  • You need autonomous triage.
  • You want to start without paying.
  • You also want duplicate detection.

Questions people ask

Is Briq or Height better?
Neither clearly leads. Briq starts at On request and Height at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Briq or Height?
Height has a free tier; the other does not. Paid plans start at On request for Briq and Free for Height.
Does Briq or Height run on more platforms?
Both run on Web, so platform support will not decide this one for you.
Can I use Height for free?
Yes. Height has a free tier, so you can try it without paying. Briq starts at On request.
What is Briq best used for?
Briq is most often used for a contractor whose month-end close runs three weeks because wip is rebuilt by hand in excel every period, a group with four operating companies on different chart-of-accounts structures that needs one consolidated margin view, a specialty contractor processing thousands of supplier invoices a month that wants coding and approval automated rather than keyed, a finance director who needs a defensible cost-at-completion forecast for a surety or lender rather than a project manager's estimate. Of those, a contractor whose month-end close runs three weeks because wip is rebuilt by hand in excel every period and a group with four operating companies on different chart-of-accounts structures that needs one consolidated margin view are not what Height is typically brought in for.
What can Briq do that Height cannot?
Briq covers Invoice capture and coding, WIP schedules, Cash flow forecasting, Cost at completion forecasting. Height covers Autonomous triage, Duplicate detection, Attribute maintenance, Per-task chat.

Answered from the vendors’ own pages

Briq: Does Briq replace my construction accounting system?

No. It reads from Vista, Sage or similar and automates the reporting and forecasting layer above them. You keep the ERP.

Height: How is this different from Jira automation?

Jira automation is rule-based: you define a trigger and an action. Height's agents read the content of tasks and act on judgement, such as recognising that two tickets describe the same bug, which no rule can express.

Briq: What does it cost?

Briq does not publish pricing. Contracts are scoped by module, entity count and transaction volume and quoted annually.

Height: Can we self-host it?

No. It is software as a service only, with no on-premises or private-cloud deployment. If your requirements rule out a hosted tracker, this is not a candidate.

Briq: How long does implementation take?

Expect months rather than weeks, because most of the work is mapping and cleaning job cost data from the existing ledger.

Height: What happens to our data if the company fails?

You would need an export and a migration to another tool. This is the standard risk with a single-product startup, and it is worth confirming the export path covers task history, comments and custom fields before committing to it.

Briq: Is it useful for a single-entity contractor?

Less so. The strongest case is multi-entity consolidation and high invoice volume; a small contractor gets thinner returns.

Height: Does it work for non-engineering teams?

Yes, the views and custom fields are generic enough for marketing, operations or support queues. Its integrations, though, are aimed at software teams, so a non-engineering team gets less of the surrounding value.

Height: Do the AI features need our tickets to be well written?

In practice, yes. Triage, deduplication and attribute maintenance work from what is written in the task, so the return is much higher on a team that already writes descriptive tickets than on one that does not.

Share

Related pages

Other head to heads