Guide · Internal tools

Build, buy or integrate?

Most teams do not need more software. They need the right piece in the right place. This page gives general criteria first, then the way we make the call in our own audits.

Buy, integrate or build: general advice.

Buy

Buy when…

  • The workflow is common.Accounting, email, calendars or a standard sales pipeline: mature products already cover it, with support and updates.
  • Your process can adapt.If changing the way you work costs less than building, adapt to the tool.
  • Speed matters more than fit.An existing product can be in use within days.

Integrate

Integrate when…

  • The tools are right but disconnected.Client details move between the inbox, the CRM and documents by copy-paste.
  • A thin layer is enough.Official APIs and automation can move data and trigger follow-ups without a new application.

Build

Build when…

  • The rules are yours.Pricing, validation or ownership rules that no standard tool understands, kept today in spreadsheets and in people’s heads.
  • Each transaction is worth a lot.The process repeats, several teams and tools are involved, and errors or delays are expensive.
  • The tools stop halfway.The CRM holds the deal, but the proposal, the checks and the follow-up happen somewhere else.

A quick grid: five questions.

  • Is the workflow standard?Yes: lean towards buying. If several mature products already do it, building rarely pays off.
  • Do the rules belong to you?Pricing, approval or ownership rules that no product models well point towards building, or towards integrating around a tool you keep.
  • Where does the friction sit?If each tool works but data is copied between them, start by integrating. If the missing step happens in nobody’s tool (spreadsheets, email), a custom layer is worth assessing.
  • What does a delay or an error cost?Compare the yearly cost of the friction (time, errors, lost deals) with the cost of building and running the solution. If the gap is small, do not build.
  • Who will run it after launch?A custom tool needs an owner for integrations, fixes and changes. Without one, prefer a product or a thin integration.

Limits of this grid.

It is general advice, not a verdict: two answers often point in different directions, and the weighting depends on your volumes, your team and your existing contracts.

Costs are estimates. Before deciding, check them against real figures: time spent per week, number of transactions, licence and running costs.

Ideas: what a custom layer on top of your tools can look like.

A dashboard for each salesperson.

Their deals, next steps and client context in one place, without opening the CRM, with every change written back.

Proposals from templates.

Generated from your pricing rules, with a template for each type of client.

One flow between tools.

Inbox, CRM and documents connected, so client data is typed once.

How our audit makes the call.

01

Map the workflow today.

Who touches it, which systems are opened, where data is copied and where people wait.

02

Find the fracture and its cost.

The bottleneck, and an estimate of its economic impact.

03

Scan what already exists.

Existing software, APIs and open source, and the smallest correct intervention.

04

Decide: go, test first, or no-go.

If a thin integration or an existing tool is enough, we say so.

What it takes.

The audit makes the call in days, not months.

Workflow audit in

3–5 days

ending with a clear build, buy or integrate decision.

First system live in

2–6 weeks

typically, connected to the tools your team already uses.

Case studies.

Business aviationJetfly AviationMarketing, sales and charter teams working in one tool, with proposals connected to the CRM.Read the case study →Media · Prisma MediaGEOMobile app journeys prototyped in Figma and tested with 200+ beta readers before development.Read the case study →Media · Prisma MediaFemme ActuelleAn A/B test lab inside the live site: new modules shown to half of the readers, kept only when they worked.Read the case study →

Questions.

Will Noctua always recommend a custom build?

No. The audit compares building, buying and integrating. If an existing tool or a thin integration solves the problem, that is our recommendation.

Who owns a custom tool?

Your data, documents, users and business rules belong to you, and the contract says so. Noctua keeps only its reusable, generic building blocks.

Do we have to replace our current tools?

No. Your CRM, email and documents remain the sources of truth. A custom layer connects them and runs the business rules between them.

Start with the workflow that hurts most.

Describe it in a few lines. Our assistant helps you frame it, then you choose: a 20-minute call, or a reply from the team by email.

or book a 20-min call