01
Planning and scheduling
What happens if another order comes in?
Change the volume, compare the hours required with available staffing, and see which part of the plan needs reviewing.
Custom applications · Built around your team
Your process deserves a better tool.
If your working day depends on copied cells, extra tabs and knowing which file is current, there may be a better way. Build a focused planning tool, portal or operational screen that fits the job.
Discuss your applicationCapacity plannerCan the team cover the plan?
Weekly packing plan4 min per unit · 32 h per person
600 units2,000 units
People available
3
Hours required80 h
Hours available96 h
16 h spareThe weekly plan fits.
Put it in the context of your work
Picture this in your business.
Different businesses. Familiar problems. Here are a few useful places to start.
02
Operations management
One place for the current status.
Give each role the records and actions it needs. Keep updates attached to the work instead of scattered across inboxes.
03
Customer or supplier coordination
A clearer way to exchange information.
Scope a controlled portal for requests, documents or progress updates, with the access rules designed around the users.
The problem
You shouldn't need five workarounds to complete one job.
A plan lives in one spreadsheet. Actual results come from another system. Staff requirements are calculated elsewhere. People copy the same information between tools and lose track of which version is current.
A custom application can connect the relevant information and give each person a clear view of the work they need to do.
What we can build
Build the tool your workflow is missing.
- Planning and scheduling tools. Work with forecasts, capacity, staffing and operational requirements.
- Internal portals. Give teams a clearer way to enter, review and manage information.
- Operational dashboards. Combine current status with the actions people need to take.
- Customer or supplier interfaces. Scope a controlled portal for an agreed exchange of information.
- Existing app improvements. Add a missing feature, improve usability or connect an application to another system.
How it works
Prove the important workflow first.
We map the users, the information and the steps the application needs to support. A first version focuses on the core workflow, with access rules and data handling included in the design.
Testing uses realistic tasks rather than only checking whether the screens look right. The handover covers the application, its dependencies and options for maintaining it.
How this service works
From an awkward spreadsheet to a plan the team can act on.
A packing team needs to see whether next week’s orders fit its available hours.Follow the example through five stages, with a clear output at each step.
01Understand
Watch how the plan is made today.
We follow the spreadsheet, the copied inputs and the decisions made from it. We ask who edits the plan, which values change and where a missing or outdated input can mislead the team.
What you take away
A workflow map, input inventory and user roles.
The starting pointStart with the inputs.
01Weekly orders
02Handling time
03Available staff hours
The question to resolveCan the team cover the workload?
02Agree
Agree the calculation and the first screen.
The first planner uses units, handling time and actual available hours. Four minutes per unit and 32 hours per person make the workload visible. We agree validation, account access and the delivery scope.
What you take away
A focused screen specification and calculation rules.
The agreed scopeA focused first result.
- Weekly units and staffing inputs
- Required and available hours
- Visible capacity gap
Keep the boundaries clear
Payroll, shift scheduling and stock control need their own agreed scope.
Confirm access, dependencies and costs before work starts.
03Build
Build around the decision the team makes.
The team reviews a working planner with editable demand and staffing. Required hours and capacity update together, making it easier to discuss the gap instead of rebuilding the spreadsheet.
What you take away
A reviewable planning screen and validated inputs.
A view to reviewMake the work visible.
First working view
01Demand · 1,200 units
02Required · 80 hours
03Available · 96 hours
Review together → refine the important details
Check it against the purpose
Does this view make the next decision clearer for the person using it?
04Test
Check the numbers at the edges as well as the centre.
We verify known workloads, demand above capacity, input limits and relevant access controls. A useful planner should explain a shortfall clearly and keep invalid inputs out of the calculation.
What you take away
Calculation checks, input validation and user-flow results.
The checks that matterThe condition changes the decision.
The input or condition1,200 units · 3 people
Expected result16 hours spare
1,200 × 4 ÷ 60 = 80 hours required; 3 × 32 = 96 available.
Agree the check. Inspect the result. Keep exceptions visible.
05Hand over
Hand over the tool and the assumptions.
The team learns how to enter the plan, interpret the result and update agreed assumptions. The handover covers hosting, accounts, data ownership and any ongoing support arrangement.
What you take away
A user guide, assumption record and ownership plan.
Ready for everyday useThe result comes with context.
Everyday tasks
Entering demand, updating staffing and interpreting the capacity result.
Assumptions & data
Handling time, available hours, input ownership and storage requirements.
Running the application
Hosting, access, maintenance and the separately agreed support route.
The next stepKnow how to use it.
Know who owns it.
Know who owns it.
Maintenance and continuing support are agreed around the project.
See the wider approach to scope, collaboration and handover.
How we work togetherA few useful answers
Questions before
the first conversation.
Can you work on an existing React application?
Yes. React and JavaScript are part of Karol's practical development experience. We inspect the codebase and current architecture before agreeing changes.
Can the app use our existing database?
Often, through a suitable API or integration. Access, performance and the data's structure need to be considered.
Should we build an app or use an existing product?
That is a discovery question. If a suitable existing product solves the problem well, custom development may not be necessary.
Can we add AI later?
Potentially. A clear data model, permission system and API make it easier to evaluate a useful AI feature without rebuilding the whole application.
The next useful conversation
What is your team working around?
Show us the spreadsheets, screens or steps that make the job harder than it needs to be.
Discuss your applicationStart with what needs to changeA report I keep rebuildingA task I keep repeatingA website we’ve outgrownSomething else entirely