Assigned to your team
JDCustom software, built around your business.
Portals, internal tools and apps built around how your team actually works.
- 6–9 weeks
- for a focused internal tool
- Every week
- working software you can use
- In writing
- scope and price, before we build
IQ/OPSAM
WORKSPACE / PROCUREMENT
2 openEverything in its place.
REQUESTSTATUS
New supplier onboardingREQ–024 · ProcurementApproved ✓
Equipment requestQueued
Contract renewalQueued
Supplier reviewAssigned to A. Morgan
Business detailsVerified ✓
Required documentsComplete ✓
✓ Approved · recorded in activity log
A request moves through its checks to a recorded approval.
01 / Sounds like you?
When the work has outgrown the workaround.
What changes
Disconnected
People, data, and tools work around each other.
One usable flow
The right information reaches the right person at the right time.
Ready to evolve
A documented product foundation that can grow with the operation.
02 / What you get
Build
The right tool for the way your team operates.
Start with one workflow that matters, or a small first version. Grow it as people use it and priorities get clearer.
Choose a capability
Different starting points. Built around your business.
IQ / CLIENT PORTALAM
Welcome to your workspace.New requestsProject enquiry
In reviewDocument check
The next action is clear
AMCompleteApproved request
Recorded and traceable
✓01 / Web applications
A portal of your own.
Apps for your customers, partners or team, with the right screens and access for each person. For example: a portal where customers send requests and track progress.
These previews are illustrative. Our published client projects so far are websites. See the work →
03 / From brief to handover
Delivery
Your call. At every step.
We gather your requirements, bring you options and say which we would pick. You choose, then we build exactly that, and you see it take shape every week.
STEP 01 / 04
Requirements
How the work runs today, who does it, what hurts, and which tools are involved.
Our advice. Your decision.IQ / PROJECT WORKSPACEIllustrative
The brief, made clear.
- 01
- The business goal
- 02
- The people involved
- 03
- The current constraint
- 04
- The first useful outcome
What you take forward.
- The app and its source code
- Docs on how it’s built and connected
- How to deploy and set it up
- A plan for who maintains it
Built in from day one.
- Map the work before the screens
- Clear roles and rules
- Plan for when things go wrong
- Built for whoever maintains it next
04 / Before we start
Questions
The details worth knowing.
Bring one workflow, the people involved and the tools it touches. A few screenshots or a spreadsheet is enough to start.
- Your business runs on a spreadsheet. Here's when that stops working.
- Build or buy? Software for a business that doesn't fit the box.
How long does custom software take?
Focused internal tools often take 6–9 weeks and first app versions 10–14 weeks. Bigger builds get a timeline once we understand them.
Can you rebuild our existing system?
Yes. We look at what you have, then replace it in stages so the day-to-day work keeps running.
How do we stay involved?
You see and use working software every week. Decisions are written down and demos are part of the routine.
Do you support the software after launch?
Yes. We can keep maintaining and improving it, or hand the code and docs over to your team.
Should we build custom software or use an existing tool?
Start with the work, not the tool. If something off the shelf fits, setting it up or connecting it may be enough. Custom makes sense when your process is too specific for generic tools.
What do you need to scope a project?
A description of the work, the people involved, the tools you use now, and the first result you need. We turn that into a written plan before we build.
What do we receive at handover?
The app, its source code and docs, plus how to deploy and run it. We also agree whether your team takes over or we keep maintaining it.