Skip to content

Solutions

Start with the problem, not the technology.

Nobody wakes up wanting “a portal” or “an integration”. What you want is for work to stop getting stuck, for people to stop typing the same thing twice, and for old software to stop holding you back. So that's how we've laid out this page.

Solution 01 / 06

Process Automation

For businesses where approvals, hand-overs and follow-ups run on email, phone calls and memory.

You'll recognize it when you hear

  • “Has anyone approved this yet?”
  • “I'll send a reminder again.”
  • “Who has the latest version?”

The problem

Most processes have clear steps on paper. In real life, they only move when someone remembers to push them. Requests sit in inboxes, approvals happen over the phone, and the only way to know where something stands is to ask the right person.

Business impact

  • Delays nobody notices until a customer or supplier complains
  • Senior people spending their day chasing instead of deciding
  • The same kind of request handled differently every time
  • No clear record of who approved what, and when

Typical use cases

  • Purchase and expense approvals, with limits by amount or department
  • Approving quotes and discounts before an offer goes out
  • Orders moving from enquiry to confirmation to dispatch
  • Job, service and maintenance requests, each with a named person responsible
  • Reviewing and signing off documents, with a full history

How Kendratek approaches it

  1. 1

    Find out how the work really happens

    Including the exceptions and shortcuts people actually use, not just the version on paper.

  2. 2

    Agree the steps, owners and rules

    Who does what at each step, what moves it on, and what happens when something waits too long.

  3. 3

    Automate the routine, keep the judgement

    Alerts, reminders and passing work to the right person happen automatically. Decisions stay with your people.

  4. 4

    Show where everything stands

    Everyone involved can see where each job is and what it's waiting for, without having to ask.

Solution 02 / 06

Business Applications

For businesses whose main work doesn't fit the shape of a ready-made product.

You'll recognize it when you hear

  • “Nobody else can update that sheet.”
  • “Which file is the right one?”
  • “We'll compile the report by Friday.”

The problem

Shared spreadsheets and general-purpose tools are a sensible place to start. But over time the whole business ends up depending on them, and they were never built to carry that weight.

Business impact

  • Important know-how sitting with just one or two people
  • Mistakes from copying, overwriting and different versions of the same file
  • Reports that take days to put together and are out of date when they arrive
  • Every bit of growth means more manual work, not more capacity

Typical use cases

  • Production planning and scheduling
  • Dealer, distributor and scheme management
  • Stock and batch tracking that follows the way you work
  • In-house systems to keep day-to-day operations under control
  • Management reports from one reliable source

How Kendratek approaches it

  1. 1

    Built around your business, not a template

    Your products, customers, rules and the words your team uses shape the software.

  2. 2

    Designed for the people who use it daily

    Screens are shaped around the people using them every day, so the new system is easier than the old way.

  3. 3

    Rules you can change yourself

    Rates, limits and categories can be changed as the business changes, without calling a developer.

  4. 4

    Delivered in stages

    We start with the part that helps most, then add to it as you learn from using it.

Solution 03 / 06

Portals

For businesses that share information with people outside the company every day.

You'll recognize it when you hear

  • “Can you check my order status?”
  • “Please resend the invoice.”
  • “Did you receive our documents?”

The problem

When customers, dealers, suppliers or field staff can only get information by asking, every simple question turns into a call or an email that someone in your office has to stop and answer.

Business impact

  • Sales and support staff giving status updates instead of doing their real work
  • Documents emailed back and forth and lost in inboxes
  • Different answers depending on who picks up the phone
  • A slower experience for the people your business depends on

Typical use cases

  • Customer portals for orders, dispatches, invoices and documents
  • Dealer and distributor portals for orders, schemes and statements
  • Supplier portals for purchase orders, deliveries and compliance documents
  • Employee and field-staff portals for requests and records

How Kendratek approaches it

  1. 1

    Work out what each group needs

    What customers, dealers or suppliers should see and be able to do, and nothing more.

  2. 2

    Use the data you already have

    The portal pulls from your existing order and accounting software, not from a separate copy that goes out of date.

  3. 3

    Everyone sees only their own

    Each person sees only their own records, and every login is controlled and recorded.

  4. 4

    Simple from the first visit

    Outside users never get training, so the portal has to make sense the first time they use it.

Solution 04 / 06

Connecting Your Software

For businesses whose programs each work fine on their own, but don't work together.

You'll recognize it when you hear

  • “Export it and I'll import it.”
  • “The numbers don't match.”
  • “Which system is correct?”

The problem

Accounting, stock, sales and other software are usually bought at different times. If they aren't linked, your people end up being the link: exporting, retyping and cross-checking the same information.

Business impact

  • Hours every week spent typing the same data again
  • Figures that don't match between programs, and take ages to sort out
  • Decisions made on numbers that are already out of date
  • Holding back on new tools because each one adds more retyping

Typical use cases

  • Linking your business software to your accounting software, such as Tally
  • Keeping orders, stock and customer details in step across programs
  • Bringing in Excel files from customers and partners, with checks for mistakes
  • Setting up secure connections with partners' systems
  • Pulling data from several places into one set of reports

How Kendratek approaches it

  1. 1

    Decide where each kind of information lives

    One master copy for each thing, so programs don't overwrite each other and nobody has to cross-check.

  2. 2

    Connect before replacing

    Software that works well stays. Linking it up is often the smaller, safer change.

  3. 3

    Plan for when things go wrong

    Checks, records and clear alerts, so if a transfer fails someone knows straight away and it gets fixed.

  4. 4

    Write it all down

    So your team understands what moves where, and future changes are safe.

Solution 05 / 06

Upgrading Older Systems

For businesses relying on older software that has become fragile, slow to change or hard to get help with.

You'll recognize it when you hear

  • “Don't touch that screen.”
  • “Only one person knows how it works.”
  • “It doesn't open on a phone.”

The problem

Older software often holds years of valuable business rules. Being old isn't the problem. The problem is when it becomes risky to change, hard to get help with, and cut off from the tools around it.

Business impact

  • Changes put off because every change feels risky
  • Depending on one person, or on technology nobody supports any more
  • No way to use it from a phone or outside the office
  • Trouble linking it to newer software and to partners

Typical use cases

  • Updating older web software (Classic ASP and early ASP.NET, for the technically minded)
  • Rebuilding older database systems so they're easy to look after
  • Making existing systems usable in a browser and on a phone
  • Linking older software to modern tools
  • Moving your data into a new system safely, with checks

How Kendratek approaches it

  1. 1

    Write down what the system really does

    Its rules, its data and the workarounds people rely on, before anything changes.

  2. 2

    Decide what to keep, rebuild, add to or drop

    Not everything needs replacing. Some parts are better added to than rebuilt.

  3. 3

    Upgrade one piece at a time

    The old system keeps running while parts are replaced one by one. No risky all-at-once switch-over.

  4. 4

    Move your data carefully

    With checks at every step, so the new system starts with data people trust.

Nearly 25 years of hands-on software work, including the older technologies many of these systems were built on, means old code doesn't scare us. It isn't automatically a reason to start over.

Solution 06 / 06

Going Paperless

For businesses where key records start on paper, forms or scattered files.

You'll recognize it when you hear

  • “It's in the register.”
  • “Fill in the form and scan it.”
  • “Ask accounts, they'll have a copy.”

The problem

Paper forms, registers and scanned documents work fine, until someone needs to find something, check it, or pull a report from it. Then it's slow to find, hard to check and almost impossible to add up.

Business impact

  • Time lost hunting for records and typing them in again
  • Missing or unreadable details discovered too late
  • No clear picture of what's pending or overdue
  • Audit and compliance preparation that takes days

Typical use cases

  • Turning paper forms and registers into simple digital forms
  • Inspection, quality and compliance records
  • Signing up new customers and suppliers, and collecting their documents
  • Recording information on a phone, out in the field
  • Collecting and tracking documents, with a clear status for each

How Kendratek approaches it

  1. 1

    Start with one process

    Pick one with a clear benefit, show it works, then move on to the next.

  2. 2

    Simplify first

    A digital copy of a pointless step is still pointless. Remove it first.

  3. 3

    Record information properly from the start

    So it can be searched, checked and reported on, not just stored.

  4. 4

    Then connect what comes before and after

    Once the first process works, link it to the steps around it.

How they fit together

Most real problems need more than one of these.

The six areas above are just a way of describing problems. They aren't separate products. A real project usually mixes two or three of them. A few examples:

  • Problem

    Dealers call for every order update

    A dealer portal is only useful if it shows up-to-date information, so it's linked to the order and accounting software you already use.

  • Problem

    Inspection records live in paper registers

    Inspectors fill in simple forms on a phone or tablet, and any failed inspection goes straight to the right person to deal with.

  • Problem

    An older order system can't keep up

    The rules built into the old system are kept, while it's rebuilt step by step around how the business works today.

Wondering how we decide what a project needs? See why businesses work with Kendratek.

Insights

Related reading.

Short, plain-English guides to read before you spend money on software.

All insights

Not sure which one applies?

Tell us the problem. We'll work out the rest.

You don't need to know anything about technology. Just tell us what's getting in the way, and we'll help you work out what makes sense.

Tell Us What You Need

Write it in your own words. A real person reads every enquiry and replies honestly, even when custom software isn't the answer.