Skip to content
Book a discovery call

Get the workflow improvement built

You know which process is causing trouble. Your team may not have the time or technical capacity to change it.

Propel designs and builds operational systems around agreed business needs. We can connect supported tools, automate repeated steps and develop internal software where an existing product is not enough.

Book a discovery call

Without Propel

Copy it across

Chase the handover

Check it again

With Propel

  1. Connected records
  2. Clear next step
  3. Your team in control

Define the result before choosing the software

The work today
What needs to change?The right tool for the job

We start with how the work happens today and what a useful improvement would look like.

For a report, that might be a checked draft with source references and a list of missing updates. For a handover, it might be a complete record reaching the right person without being retyped.

We then check whether the benefit justifies the implementation effort and ongoing cost. AI is useful for some tasks. Fixed rules or a change to an existing tool may be the better answer for others.

What an implementation includes

  1. Written scope
  2. Build & test
  3. Reviewed handover

The written scope names the workflow, users, input sources and expected outputs. It explains which systems we will connect and what access your team needs to provide.

We design the process, build the agreed components and test them against representative examples. Testing covers the normal task and what happens when information is missing, duplicated or wrong.

Before launch, we review the result with you against agreed acceptance checks. Handover includes practical guidance, relevant access and documentation for running the delivered system.

Keep control of important actions

  1. Prepared output
  2. Human approval
  3. Agreed action

We agree where a person needs to review or approve an output. That can include checking a report, approving a customer message or deciding how to resolve an exception.

Permissions should match the task. A system gathering information does not automatically need permission to edit records or contact customers.

The design also needs a visible failure state and a way for your team to continue the work manually.

How the project moves forward

  1. Review the current work

    Show us a recent example and explain what makes it difficult. We identify the people, systems and constraints involved.

  2. Agree the scope and price

    We check feasibility and set out the deliverables, exclusions, client responsibilities and payment terms. A paid audit is only needed if the uncertainty warrants a separate investigation.

  3. Build and test

    We develop the agreed solution and review progress at the stated milestones. Changes to requirements are discussed and priced before we add them.

  4. Launch and hand over

    We agree when the system can go live, explain how to use it and document who will maintain it. The proposal defines correction and support arrangements.

Price and timing

Your proposal
Scope & priceDelivery scheduleSeparate running costs

Implementation is quoted individually. The number of systems, data quality, permissions and testing requirements all affect the work.

We agree the price and delivery schedule after checking the scope and access. Software subscriptions, hosting and usage charges are identified separately where applicable.

Understand implementation costs

Questions before a build

Do we have to replace our software?

Not necessarily. We first check whether the tools you already use can support the change. Some connections require a different subscription, vendor approval or custom development. We confirm those dependencies before quoting the work.

Will we own the system?

The proposal explains ownership of commissioned work, account access and third-party licences. We identify any components that remain subject to a supplier's terms before you commit.

Can you promise a saving?

We can assess the opportunity with you and agree how to measure it. We cannot promise a standard saving before understanding the process. Time released only becomes a cash saving if it changes an actual cost.

What happens after handover?

Your agreement states the correction period and support included. Ongoing monitoring or improvements need a defined support agreement. We do not offer 24/7 support under our standard service.

Tell us what is waiting to be fixed

Bring a process, an example and the person who knows how it works. We will discuss whether a scoped implementation is a sensible next step.

Book a discovery call