Skip to content
Samlution

Offer 04 · Custom

When the workflow is the business, the software should fit it.

Client portals, internal tools and operational platforms designed around how your firm actually works — not bent to fit a template.
Project fee
Scoped per engagement
Typical duration
From 6 weeks
Scope
Fixed, written
Approval
Human, always

How the engagement runs

Custom Business Platforms · From 6 weeks

  1. The work today: The process exists, but it is spread across inboxes, shared drives and whoever remembers.
  2. Discovery: A paid session maps the current steps, handoffs and exceptions, and takes a baseline.
  3. Build in milestones: Work ships in visible increments with review points, so a wrong assumption is cheap to change.
  4. Approval gate: Anything client-facing waits for a person. The gate is part of the build, not an afterthought.
  5. Handover: A working system in your accounts, with documentation and a session for the team.
  6. Measure: The outcome is compared with the original baseline, then you decide: optimise, expand, or stop.
One path from manual work to a measured result. The approval gate is deliberate: preparation can be automated, the commitment to a client cannot.

The situation

What this engagement actually changes.

Some processes are too specific to buy off the shelf and too important to run in spreadsheets. This is the engagement for the systems that sit at the centre of your delivery.
  • One system of record for the process, instead of three partial views
  • Roles and permissions that match how the team is actually structured
  • An audit trail behind every state change
  • Documentation and handover, so the platform is not a black box

Best for

  • Firms running a core delivery process across spreadsheets and email
  • Teams that need a client-facing portal with permissions and audit history
  • Businesses whose existing tools almost work, but force manual workarounds

What we need from you

  • A sponsor who can make decisions within a week
  • Access to the people who perform the process today
  • A willingness to ship in phases rather than one large launch

Fee

Scoped per engagement

Timeline

From 6 weeks

Scope

What you get, in plain language.

Each line below is a deliverable you can review at handover. Nothing here is optional or assumed.
01

Discovery & process mapping

The current process, its exceptions and the decisions the system must support.

02

Data model & system design

Entities, states and permissions agreed before interface work begins.

03

Custom portal or internal tool

A focused interface for the people who do the work every day.

04

Integrations

Connections to your CRM, storage, billing or communication tools.

05

Roles, permissions & audit

Access by role, with a record of who changed what and when.

06

Handover & documentation

Architecture notes, credentials in your ownership and a team walkthrough.

What is not included

Written down before we start, so it never becomes a surprise invoice.

  • Ongoing hosting, inference or third-party licence fees beyond an agreed managed plan
  • Features invented after scope sign-off, except through a change request
  • Design work for brand systems unrelated to the platform

How it works

Discover, design, build, improve.

Clear scope, human oversight and measurable outcomes. Every engagement follows the same four stages, whether it takes two weeks or two months.
01

Discover

Understand the process before proposing a tool.

Output

A written problem statement and a shortlist of options, including the option of doing nothing.

02

Design

Choose the smallest system that solves the problem.

Output

A signed scope with deliverables, exclusions and a fixed payment schedule.

03

Build

Ship in visible increments, with your team involved.

Output

A working system in your accounts, with documentation and a handover session.

04

Improve

Measure the outcome, then decide what is next.

Output

An outcome report and a decision on whether to move to a managed service.

Questions

About the custom platforms.

Why not just use an existing SaaS tool?
Sometimes you should, and we will say so. A custom build makes sense when the process is a source of competitive advantage, when no tool fits the handoffs, or when manual workarounds are costing more than building.
How is scope controlled?
Written scope, milestones and acceptance criteria before build. Changes are estimated and approved before anyone starts them.
Who owns the code?
Ownership of source code, configuration, customer data and reusable components is defined explicitly in the agreement — no assumptions in either direction.

Next step

Start with custom platforms.

A 30-minute call to confirm the scope, the timeline and whether this is genuinely the right first step.

No obligationFixed scope, fixed feeApproval stays human

See how engagements run