LoomTech

Built to order

The systems we build to order

We have built these before. Each one is shaped to how the business already runs rather than configured out of somebody else's product, and it talks to what you already use. Built in Colombo, by the people who then keep it running. What yours needs is settled in the first conversation; the parts below are where most builds start.

Tell us what you need

ERP: what you hold and what it cost

For a business whose money sits in parts and stock. It answers the two questions a workshop asks every day: can we start this job, and did we make anything on the last one.

  • Stock and parts

    What is on the shelf, what is held against a job, and what to order before it runs out

  • Purchasing

    Supplier prices, purchase orders, what arrived, and what is still owed

  • Costing per job

    Parts, labour and time against the job, so the margin on it is a number and not a feeling

  • Suppliers

    Lead times and the price you actually paid last time, beside the one you were quoted

  • Locations

    Stock split across the shop, the store room and a van, each counted on its own

  • Stock counts

    A count read against what the system expected, and every difference written down

CRM: who asked, and what was promised

For a business that quotes before it works. Every enquiry, quote and conversation stays against the company, so a price agreed on the phone in March is still findable in September.

  • Contacts and companies

    Every person, number and address on one record, and who at the company asked for what

  • Pipeline

    Enquiries through to a won job, each one sitting at the stage it has reached

  • Quotes

    What was quoted, what was agreed, and every change between the two

  • History

    Calls, messages and visits against the company, so anyone picking it up is current

  • Follow-ups

    A reminder that sits on the record, where whoever picks it up next will find it

  • Segments

    Everyone who bought a particular thing, or who has not been back since March, as a list you can act on

Order management: ordered to delivered

For a business that ships. It follows one order from the price that was agreed to the signature at the door, including the awkward middle where half of it goes out this week.

  • Orders

    What was ordered, at what price, and who agreed it

  • Picking

    What has been pulled, what is short, and what went out as a substitute

  • Part shipments

    An order that leaves in two deliveries stays one order the whole way through

  • Dispatch

    Who took it, when it left, and the signature or photograph that says it arrived

  • Pricing

    The list price, the rate this customer is on, and what an agreed discount did to the margin

  • Returns

    What came back and why, and whether it was replaced, repaired or refunded

In every build, not a tier

Whichever of the three you start with, these six come with it from the first day. They are the parts a business finds it needs in the second month, so they are there in the first.

Reports you can take away

Every figure on screen downloads as a spreadsheet or a PDF, on a schedule or whenever you want it.

Your customer database stays yours

Your customers, your records. Export the lot at any time, in a format another system can read.

Secure storage and logins

Secure storage, authenticated logins, secure APIs, and a role per person so the counter does not see the margins.

It connects to what you run

A full API, so records pass between this, your accounts package and either of our products.

An audit trail on every record

Who changed what, and when. A disagreement about a price or a date is settled by the record.

We train the people using it

We sit with the counter and the office until they are working in it. Training is part of the build.