Briq

Name: Briq
Brand: Briq
Rating: 3.6 (18 reviews)

Briq is the creator of Otto, an AI orchestration platform for physical industries.

Est 2018|Valuation $248M|Raised $51M|27 Ref Customers

LinkedIn 120K|Web traffic 5K|FTEs 125|HQ Santa Barbara, California, US

Published Oct 15, 2026

01Common complaints

1. Organizations that require guaranteed, rapid implementation with low variance. Multiple detailed reviews allege prolonged or non-functional implementations. 2. Organizations that require flexible refund policies or outcome-based contracting. Customer complaints reference contract rigidity and non-refundable fees. 3. Organizations whose primary need is broad construction project execution management (RFIs, submittals, field productivity, document workflows). Platforms such as Procore or Autodesk Build may be more appropriate as primary systems in those cases. 4. Environments that are highly customized and integration-sensitive. Several reviews identify integration as a principal failure mode. 5. Organizations with limited budgets that cannot accept implementation risk. In such cases, narrower tools (single-purpose AP automation or reporting/BI tools) with faster proof-of-value may be preferable.

Deal disqualifiers (poor fit)

Organizations requiring plug-and-play integrations with minimal implementation effort.
Environments with highly customized or legacy systems that are difficult to integrate.
Organizations that cannot tolerate variable time-to-value or require guaranteed, rapid outcomes.

Known limitations indicated by market evidence

- Integration variability: some users describe integration as tedious, while others report failed or non-functional integrations. - Customization constraints: at least one reviewer flags limits in tailoring workflows. - Limited public transparency: security is partially documented (SOC announcements), but detailed security controls, hosting, and data residency information are not clearly published in available sources. - Limited review volume on some platforms (e.g., low number of G2 reviews) reduces confidence that average ratings are representative.

Vendor-acknowledged items / roadmap

Public sources did not include a detailed product roadmap. Buyers should request:

product roadmap commitments with timelines,
a reference architecture for integrations,
proof-of-concept scope and acceptance criteria.

Where it struggles (based on reviews)

Integration with certain accounting systems and moving matched transactions into accounting tools (one reviewer reports an inability to match POs/invoices and push into QuickBooks Online).

02Why they buy

Differentiators supported by evidence

Construction-focused finance automation with an emphasis on forecasting and back-office workflow automation as emphasized in vendor materials and press coverage.
A vendor-presented agent/bot-based automation approach (AutoPilot) combined with forecasting and risk detection functionality (CoPilot) which differs from pure BI tools.
Security baseline signals: SOC 2 Type II announcement and SAML SSO support are relevant to enterprise buyers.

Where competitors clearly have advantages

Procore and Autodesk: broader platform breadth, larger ecosystems, and more extensive market presence.
Specialist AP automation vendors: may provide more standardized, repeatable AP implementations with established performance metrics.

Why customers chose Briq (themes)

Across positive reviews and case studies, buyers selected Briq for:

reducing manual entry and consolidating financial insights,
automating reporting and forecasting (e.g., WIP-like reports),
connecting data from ERP and project management systems into a combined operational-finance view.

03Field reports

Review platform coverage (G2 and Capterra)

G2: - Well rated on G2 with limited review volume. Representative positive feedback (G2): - "briq has automated entire budgeting and forcasting for my business." Representative criticism (G2): - "initial integration… was difficult" - Mentions integration challenges and customization limitations. Capterra: - Capterra listing shows an overall rating reported in the sources. Representative positive feedback (Capterra): - "helped us make smarter, faster decisions and saved us a lot of time and money." (Controller) - "light years ahead of Microsoft Excel." (Project Manager) Representative negative feedback (Capterra): - One reviewer described prolonged failure to deliver a promised PO/invoice matching workflow and alleged a significant paid amount. - Another reviewer alleged software not working months after contract signing and no refund. - Other reviews describe the software as incomplete, criticize upsell attempts and contract increases. - A reviewer advised ensuring the product functions for their use case before buying and described failed integrations and refund disputes. Notes: Customer quotes are included as representative feedback from review platforms. They reflect a range of experiences and, in some cases, charged language or hyperbole used by individual reviewers.

Why some customers left or warned others (churn risk themes)

The most severe negative reviews highlight:

implementation not delivering functional outcomes after months,
integration failures with accounting systems,
perceived rigidity around refunds and contract terms,
frequent staff turnover during implementation (as perceived by reviewers).

Outcomes achieved (with metrics when available)

Vendor materials and social posts contain claims regarding the number of workflows/tasks automated and estimated contractor savings. These claims were not independently verified in the sources captured here.
A vendor case study reports improvement in cash position following implementation of an automated JCCM report, but the case study does not provide a transparent ROI methodology or third-party validation.

Case study: a regional builder

- Context: A regional builder used Sage Intacct (ERP) and Procore (PM) but reported difficulty producing key reports like JCCM and WIP. - What Briq did: Worked with the builder to identify data sources and build an automated JCCM first, then planned WIP automation. - Reported outcome: Improved real-time visibility and a reported improvement in cash position. Critical evaluation: - The benefits described are plausible (automation of financial reporting can reduce manual cycles), but the case study is vendor-authored and does not quantify ROI with a transparent method. - Reported improvements depend on correct data mapping across Sage Intacct and Procore; buyers with different ERPs or PM tools may not replicate the same results.

Acquisition-driven capability expansion: Swipez

Briq's acquisition of Swipez was presented as an effort to expand into accounts receivable and billing automation.

Critical evaluation:

The acquisition could extend capabilities into AR and billing collection workflows, but buyers should clarify whether features are native or integrated post-acquisition and whether workflows are supported for their ERP and billing processes.

04Best fit

Company size

Likely fit: organizations roughly in the mid-market to larger enterprise range, or smaller firms with high transaction volume or process complexity that justify multi-thousand-dollar annual contracts.

Industries/verticals

Commercial construction contractors and companies managing multiple projects with complex cost codes, WIP-style reporting needs, and tight margin management requirements.

Roles/personas

Decision makers:

CFO, Controller, VP Finance
CIO / IT Director (integration/security)

End users:

Project accountants
Financial analysts
Project managers needing financial visibility

Qualification criteria (good fit)

Clear, high-volume workflows to automate (AP allocations, job cost reporting, forecasting cadence).
Stable, well-configured ERP/PM systems with clean master data.
Willingness to invest in implementation and change management.

05The pitch

What the product does (objective value proposition)

Briq is a construction-focused financial automation and forecasting platform. It operates as a layer that connects to existing construction systems (e.g., ERPs and project management tools) and uses automated agents (referred to in vendor materials as "digital workers") plus analytics and machine learning models to: - automate deterministic back-office finance workflows (commonly AP/AR/payroll-related processes), and - improve forecasting, reporting, and visibility for project financials (e.g., job cost forecasting, revenue recognition, WIP-style reporting). Vendor materials and public coverage reference modules described as AutoPilot (automation of repetitive workflows) and CoPilot (forecasting/risk detection), and more recent references to an Otto AI Autonomous Work Platform. Public statements describe a bot library and claims of automating a substantial share of tasks in certain workflows.

Target market and market positioning

Briq targets: - General contractors and construction businesses that run complex, project-based financial operations. - Mid-market to enterprise construction organizations with sufficient transaction volume and process complexity to justify automation and a paid implementation. Positioning themes in public materials and press coverage include: - replacing spreadsheet-driven processes for forecasting and reporting, - reducing labor requirements associated with back-office financial workflows, and - connecting data across ERP and project management systems to improve visibility.

Get a comprehensive analysis of Briq including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 15, 2026

01Common complaints

Organizations that require guaranteed, rapid implementation with low variance. Multiple detailed reviews allege prolonged or non-functional implementations.
Organizations that require flexible refund policies or outcome-based contracting. Customer complaints reference contract rigidity and non-refundable fees.
Organizations whose primary need is broad construction project execution management (RFIs, submittals, field productivity, document workflows). Platforms such as Procore or Autodesk Build may be more appropriate as primary systems in those cases.
Environments that are highly customized and integration-sensitive. Several reviews identify integration as a principal failure mode.
Organizations with limited budgets that cannot accept implementation risk. In such cases, narrower tools (single-purpose AP automation or reporting/BI tools) with faster proof-of-value may be preferable.

Deal disqualifiers (poor fit)

Organizations requiring plug-and-play integrations with minimal implementation effort.
Environments with highly customized or legacy systems that are difficult to integrate.
Organizations that cannot tolerate variable time-to-value or require guaranteed, rapid outcomes.

Known limitations indicated by market evidence

Integration variability: some users describe integration as tedious, while others report failed or non-functional integrations.
Customization constraints: at least one reviewer flags limits in tailoring workflows.
Limited public transparency: security is partially documented (SOC announcements), but detailed security controls, hosting, and data residency information are not clearly published in available sources.
Limited review volume on some platforms (e.g., low number of G2 reviews) reduces confidence that average ratings are representative.

Vendor-acknowledged items / roadmap

Public sources did not include a detailed product roadmap. Buyers should request:

product roadmap commitments with timelines,
a reference architecture for integrations,
proof-of-concept scope and acceptance criteria.

Where it struggles (based on reviews)

Integration with certain accounting systems and moving matched transactions into accounting tools (one reviewer reports an inability to match POs/invoices and push into QuickBooks Online).

02Why they buy

Differentiators supported by evidence

Construction-focused finance automation with an emphasis on forecasting and back-office workflow automation as emphasized in vendor materials and press coverage.
A vendor-presented agent/bot-based automation approach (AutoPilot) combined with forecasting and risk detection functionality (CoPilot) which differs from pure BI tools.
Security baseline signals: SOC 2 Type II announcement and SAML SSO support are relevant to enterprise buyers.

Where competitors clearly have advantages

Procore and Autodesk: broader platform breadth, larger ecosystems, and more extensive market presence.
Specialist AP automation vendors: may provide more standardized, repeatable AP implementations with established performance metrics.

Why customers chose Briq (themes)

Across positive reviews and case studies, buyers selected Briq for:

reducing manual entry and consolidating financial insights,
automating reporting and forecasting (e.g., WIP-like reports),
connecting data from ERP and project management systems into a combined operational-finance view.

03Field reports

Review platform coverage (G2 and Capterra)

G2:

Well rated on G2 with limited review volume.

Representative positive feedback (G2):

"briq has automated entire budgeting and forcasting for my business."

Representative criticism (G2):

"initial integration… was difficult"
Mentions integration challenges and customization limitations.

Capterra:

Capterra listing shows an overall rating reported in the sources.

Representative positive feedback (Capterra):

"helped us make smarter, faster decisions and saved us a lot of time and money." (Controller)
"light years ahead of Microsoft Excel." (Project Manager)

Representative negative feedback (Capterra):

One reviewer described prolonged failure to deliver a promised PO/invoice matching workflow and alleged a significant paid amount.
Another reviewer alleged software not working months after contract signing and no refund.
Other reviews describe the software as incomplete, criticize upsell attempts and contract increases.
A reviewer advised ensuring the product functions for their use case before buying and described failed integrations and refund disputes.

Notes: Customer quotes are included as representative feedback from review platforms. They reflect a range of experiences and, in some cases, charged language or hyperbole used by individual reviewers.

Why some customers left or warned others (churn risk themes)

The most severe negative reviews highlight:

implementation not delivering functional outcomes after months,
integration failures with accounting systems,
perceived rigidity around refunds and contract terms,
frequent staff turnover during implementation (as perceived by reviewers).

Outcomes achieved (with metrics when available)

Vendor materials and social posts contain claims regarding the number of workflows/tasks automated and estimated contractor savings. These claims were not independently verified in the sources captured here.
A vendor case study reports improvement in cash position following implementation of an automated JCCM report, but the case study does not provide a transparent ROI methodology or third-party validation.

Case study: a regional builder

Context: A regional builder used Sage Intacct (ERP) and Procore (PM) but reported difficulty producing key reports like JCCM and WIP.
What Briq did: Worked with the builder to identify data sources and build an automated JCCM first, then planned WIP automation.
Reported outcome: Improved real-time visibility and a reported improvement in cash position.

Critical evaluation:

The benefits described are plausible (automation of financial reporting can reduce manual cycles), but the case study is vendor-authored and does not quantify ROI with a transparent method.
Reported improvements depend on correct data mapping across Sage Intacct and Procore; buyers with different ERPs or PM tools may not replicate the same results.

Acquisition-driven capability expansion: Swipez

Briq's acquisition of Swipez was presented as an effort to expand into accounts receivable and billing automation.

Critical evaluation:

The acquisition could extend capabilities into AR and billing collection workflows, but buyers should clarify whether features are native or integrated post-acquisition and whether workflows are supported for their ERP and billing processes.

04Best fit

Company size

Likely fit: organizations roughly in the mid-market to larger enterprise range, or smaller firms with high transaction volume or process complexity that justify multi-thousand-dollar annual contracts.

Industries/verticals

Commercial construction contractors and companies managing multiple projects with complex cost codes, WIP-style reporting needs, and tight margin management requirements.

Roles/personas

Decision makers:

CFO, Controller, VP Finance
CIO / IT Director (integration/security)

End users:

Project accountants
Financial analysts
Project managers needing financial visibility

Qualification criteria (good fit)

Clear, high-volume workflows to automate (AP allocations, job cost reporting, forecasting cadence).
Stable, well-configured ERP/PM systems with clean master data.
Willingness to invest in implementation and change management.

05The pitch

What the product does (objective value proposition)

automate deterministic back-office finance workflows (commonly AP/AR/payroll-related processes), and
improve forecasting, reporting, and visibility for project financials (e.g., job cost forecasting, revenue recognition, WIP-style reporting).

Vendor materials and public coverage reference modules described as AutoPilot (automation of repetitive workflows) and CoPilot (forecasting/risk detection), and more recent references to an Otto AI Autonomous Work Platform. Public statements describe a bot library and claims of automating a substantial share of tasks in certain workflows.

Target market and market positioning

Briq targets:

General contractors and construction businesses that run complex, project-based financial operations.
Mid-market to enterprise construction organizations with sufficient transaction volume and process complexity to justify automation and a paid implementation.

Positioning themes in public materials and press coverage include:

replacing spreadsheet-driven processes for forecasting and reporting,
reducing labor requirements associated with back-office financial workflows, and
connecting data across ERP and project management systems to improve visibility.

Get a comprehensive analysis of Briq including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →