hakubase
IT / EN
Get started

Your work in one platform.

Sales, marketing, projects and hours, support with SLAs, client portal, invoices. The quote becomes a project, the hours become an invoice, and nobody re-enters anything.

Get started Book a demo See the cycle ↓
The Hakubase dashboard The Hakubase dashboard
  • 20 modules, one cycle
  • 1 price per person
  • EU data, backup and restore
Why it exists

Today you have two options. Neither one works.

Option one
The enterprise suite

Powerful, expensive, slow to set up. You pay per seat, for modules you will never use.

Option two
Five separate tools

The CRM, the project tool, the timesheet, the accounting system, the spreadsheets. The real cost is not the subscription: it is keeping them aligned by hand. Hours get lost, data gets entered twice, the margin shows up at year end.

Hakubase
One platform, without the complexity

Hakubase covers the gap in between: sales, delivery, planning and billing in one system, without enterprise complexity.

The cycle

A flow that supports, never forces.

Lead
Deal
Quote
Contract
Project
Delivery
Invoice
Margin

The sequence describes the full path, not a constraint. Every entity can be created on its own: a customer that was never a lead, a project with no contract behind it, an invoice for work born outside the system.

When the path is there, the system follows it. Always a proposal, never an obligation — and every link can be established later, on entities born apart.

What happens when a quote is accepted 3 automations
The contract is created
With value, start date and recurring items pre-filled from the quote lines.
The project is opened
One task for each catalog service, assigned to its default owner.
The deposit enters the billing queue
Nothing is invoiced without confirmation.
Planning

Delivery gets planned. With real hours.

Every project enters one plan: a Gantt with dependencies and critical path, per-person capacity, holidays and company closures. Overload shows up before it becomes a delay.

Explore planning →
Features

A module for every stage. A stage for every module.

Every feature has its own page. These are the main ones.

Sales pipeline
The pipeline that needs no upkeep.

Leads and deals, list and kanban

→
Quotes
From catalog to PDF, in minutes.

From catalog to tracked PDF

→
Contracts
The contract is born from the accepted quote.

Value, recurrence, signature

→
Projects and tasks
The project starts from the contract. Or on its own.

List, kanban, Gantt, hours

→
Planning
The right people, on real dates.

Gantt, capacity, critical path

→
Support
Support inside the cycle, not beside it.

Tickets, SLA, hours

→
Billing
Nothing goes out on its own. Nothing gets forgotten.

A queue fed by the cycle

→
Costs and margins
The real margin, not the hoped-for one.

Actual margins, measured

→
Automations
When X happens, Hakubase does Y.

Visual workflow editor

→
All features
Principles
01
Cycle coherence

Features do not live in silos. What happens in one is reflected in the others, with no manual re-entry.

02
Self-evident before complete

Value within the first fifteen minutes, with no long wizards and no training.

03
Extensible instead of exhaustive

Public API, webhooks and custom fields as the standard answer to niche needs.

04
Nothing gets lost

Every entity has a full timeline. Nothing is destructively deleted. History is complete.

Extensibility

Public API, webhooks, custom fields.

Niche needs do not become modules: they become extensions. Versioned API, outgoing webhooks on every domain event, custom fields on every entity.

webhook · offer.accepted 
POST https://example.com/hooks/hakubase

{
  "event": "offer.accepted",
  "workspace": "marchesi-partners",
  "data": {
    "offer": "OFF-2026-041",
    "customer": "Fornace Nord",
    "amount": 24800,
    "proposes": ["contract", "project"]
  }
}
Built to stay.

Start on your own with the trial, or let us walk you through it.

Book a demo or start the trial →

No newsletter. We only write to set up the demo.