Custom software
Custom development
Fill the gaps of your current processes with custom-built solutions.
Example
See an example
Illustrative builds, start to finish: where the work leaves the system, what gets built, and what changes. Pick one.
Before
Tracker workbook
Kept on a shared drive
Copies by email
Sent round for updates
Merged copy
Versions combined by hand
Status meeting
Works from whichever copy is newest
After
Web app
One form for everyone who fills it in
Copies by email
Nothing to send round
One shared record
Behind every screen
Live list
Current for whoever opens it
01
Where it breaks
A job none of your software covers ends up in a workbook. Copies go round by email, someone merges them, and the version in the meeting is already out of date.
02
What gets built
A small web app shaped around that one job: a form for the people who fill it in, a list for the people who check it, and one record behind both.
03
What changes
Everyone works on the same record, nothing is merged by hand, and the tracker no longer depends on the one person who understands the workbook.
Before
First system
Where the data is entered
Export
Pulled out to a file
Spreadsheet
Reshaped by hand
Second system
Keyed in again
After
First system
Where the data is entered
Link
Moves the data across in the shape the second system expects
Spreadsheet
No reshaping by hand
Second system
Kept in step by the link
01
Where it breaks
Two systems hold the same information, and the only bridge between them is a person with an export, a spreadsheet and an afternoon.
02
What gets built
A link between the two that moves the data across in the shape the second system expects, so neither system has to change how it works.
03
What changes
The data is entered once. The export, the reshaping and the second round of typing drop out of the week.
Before
Daily sheet
Quantities written up by hand
Spreadsheet
Keyed in at the office
Cost system
Keyed in again
Weekly report
Runs on last week’s numbers
After
Field form
Quantities logged against the work package
Spreadsheet
No longer in the path
Cost system
Updated as they are logged
Report
Runs on today’s numbers
01
Where it breaks
Progress lives on paper until someone in the office types it into a spreadsheet, then types it again into the cost system. By the time the report runs, the numbers are days old.
02
What gets built
A short form for the field, listing the work packages already set up in the cost system. A foreman picks one, logs the quantity, and it is written straight across.
03
What changes
No spreadsheet in the middle and nothing new for the office to learn. The cost system stays the record, and the report runs on what was installed today.
The process
How the work runs
One gap at a time, with working software in front of your team early, so you decide what comes next on something you have used.
- 01
Walk the process
We sit with the people doing the work and map where it leaves the system: the re-keying, the side spreadsheets, the email chains.
- 02
Pick the gap
Together we choose the gap that costs the most time or trust, and agree what done looks like before anything is built.
- 03
Build in short rounds
Crews and the controls team try each working version on real project data, and steer it while it is still cheap to change.
- 04
Run it alongside
It goes live next to the systems you already run, and we stay on to support it and take on the next gap.
Who does the work
The ControlPAK team: product managers, engineers and data analysts, each in their own words on our team page.
Product and operations
Find the gaps and issues in a process, turn them into tools people actually want to use, and keep the work running smoothly.
Monica Cantu, Rhett McCall, Kade McCall
Engineering
Design, build and support the software across its life, and make cost data and schedules talk to each other.
Juan Mendez, Kyle Nguyen, Waheed Abdul, Laila Rojas
Data
Turn messy project data into clear information, and find the bottlenecks in how the work gets done.
Caitlin Eidson, Wyatt Chase, Caden Hendricks, Mason Daniels, River Orsak, Mason Dooley
In practice
What it looks like
Fits when
- The field and the office are working from different pictures
- Your tools do not talk to each other
- 01
Utility apps for the jobs your current software does not cover
- 02
Links between the systems you already run
- 03
Web apps to replace the spreadsheets and macros a job runs on
Also from ControlPAK
Talk it through with someone who has run these projects
Tell us what you are working with and we will tell you whether this fits.
Talk to our team