WorkLiltBy Michael Wilson, founder of WorkLilt · Updated 7 October 2026
Start with one recurring problem
A growing list of features can hide the reason you wanted software in the first place. Choose one recurring problem: finding the latest job update, knowing who owns a task, keeping project details together or locating an item in a yard. Describe what happens today and what should happen instead.
For example, a delivery task might currently be passed around a message group. A useful first workspace would show one owner, the delivery status and the next action. You can explore that pattern in our job management example.
Write down who needs to see what
List the people who create records, update them, make decisions and simply need to know what is happening. They may not all need the same screen or the same access. Ask each person what they need to finish their own part of the job.
Separate a shared team update from a commercial decision or a confidential record. Agree access requirements before loading real business information. A smaller, relevant view is often easier to use than a dashboard showing every possible field.
Choose the information that changes a decision
For a job, start with the task name, owner, status and next action. Add a due date or supporting detail when someone actually uses it. For a project, decide which updates, documents and decisions need a shared home. For operations, define the areas and the items associated with them.
Every field creates work for someone. Ask who will keep it current, when they will update it and what happens if it is wrong. If no one can answer, leave it out of the first scope or make it optional.
Decide which tool is the source of truth
Existing email, accounting software and document folders may remain essential. Before introducing another workspace, decide where each record is maintained. Avoid asking the team to update the same information in several places without a clear reason.
Do not assume an integration is available because two products both hold similar data. Access, supported interfaces and the direction of updates need to be checked. At WorkLilt, integrations and difficult migrations receive a separate assessment and quote.
Compare software using a real task
Use the same example when comparing products. Create a job, assign it, find it on a phone, update the status and check what another team member sees. Ask someone who will use the software every day to try it without you explaining every button.
Record where they hesitate. Look for clear navigation, readable text, useful search and a straightforward next action. A polished demonstration helps, but your own workflow is the better test of whether a tool fits.
Agree scope, cost and handover
Write down the first workflow, included features, users, sample data and acceptance checks. Confirm setup costs, ongoing hosting and support, how changes are priced and what happens when the service ends. Ask about access, data handling and recovery arrangements before committing.
WorkLilt’s £1,500 starter setup applies to a defined scope using existing features. Monthly support is additional. Larger work, new modules and integrations are quoted separately. Review the support and data arrangements alongside the price.
Review the first workflow before expanding
Use a manageable set of accurate records and test the whole process with the people involved. Check that jobs have owners, updates are current and the team can find what it needs. Agree who maintains the information and how feedback is collected.
Once that workflow works in practice, decide what to add next. See how WorkLilt builds and reviews a workspace, or discuss your team’s first software workflow with Michael.