ArquetWhere business logic becomes software
Arquet
Custom B2B software

Software built around
how your business works.

Custom operational software for B2B companies that have outgrown spreadsheets and disconnected tools.

Discuss your project→See what we build
app.yourcompany.com interactive
WorkspaceOverview

Overview

+4.2%
+8.4%
-2.1%
+16.8%
12m30d7d
Active
Pending
Active
  1. Process
  2. Rules
  3. System
What we do

We turn your process into a working system.

  1. Process
  2. Rules
  3. Roles
  4. Decisions
  5. System
Business workflow modeled as softwareA request is received, validated, assigned to an owner and reviewed. If approval is needed a manager signs off, then a task is created, the client is notified, the work moves to in progress, is completed and a follow-up is scheduled. Incomplete requests loop back to ask the client for details.
What we build

Operational software for real business workflows.

  1. 01

    Internal operations

    Workflows, records, and responsibilities in one place.

  2. 02

    Customer & supplier portals

    One structured place to exchange requests and documents.

  3. 03

    RFQ & quotation systems

    Requests, quotes, and follow-up through a defined flow.

  4. 04

    Workflow & approval

    Multi-step processes with roles, statuses, and sign-off.

  5. 05

    Custom CRM

    Built around the way your company actually sells.

  6. 06

    Dashboards

    A clear view of the information that runs the operation.

Something else? If the workflow can be defined, it can be built.

Tell us what you need
Backend architecture

Good software starts with a good data model.

The structure of the data should follow the structure of the business.

  1. Business
  2. Entities
  3. Relationships
  4. Rules
  5. Application
arquet / backend
workspace · procurement
Database Tables (6)schema
accounts#2
{
  • id: integer
  • created_at: timestamp
  • name: text
  • plan: enum
  • approval_limit: decimal
}
users#4
{
  • id: integer
  • created_at: timestamp
  • account_id: integer
  • email: email
  • role: enum
}
requests#7
{
  • id: integer
  • created_at: timestamp
  • account_id: integer
  • title: text
  • status: enum
  • created_by: integer
}
offers#9
{
  • id: integer
  • created_at: timestamp
  • request_id: integer
  • supplier_id: integer
  • amount: decimal
  • status: enum
}
approvals#12
{
  • id: integer
  • created_at: timestamp
  • request_id: integer
  • approver_id: integer
  • decision: enum
}
documents#15
{
  • id: integer
  • created_at: timestamp
  • request_id: integer
  • file: attachment
  • visibility: enum
}
POST/offers
  1. POST /offers
  2. GET /requests
  3. PATCH /requests/:id
Inputs
  • request_idinteger
  • amountdecimal
  • notestext
Validate offer
  • Preconditionamount > 0
  • Preconditionsupplier.role
Get Record
requests
Return asrequest
Database Transaction
  • Add Recordoffers
  • Edit Recordrequests
Return asoffer
Response
offer
Status201
Our process

Chaos in. System out.

  1. Scattered

    Understand

    Map people, rules, and data.

  2. Structured

    Structure

    Define the model before code.

  3. Connected

    Build

    Wire interface, backend, and data.

  4. Running

    Test

    Run real workflows, then refine.

Who it is for

Built for operationally complex B2B companies.

  • Supply & distribution
  • Manufacturing
  • Construction & engineering
  • B2B services
  • Professional services
  • Agencies
Why custom software

Your operation does not always fit inside someone else's software.

Instead of adapting the operation to the software, the software adapts to the operation.

Off the shelf
  1. Your process
  2. Generic software
  3. Workarounds
Custom
  1. Your process
  2. Custom software