The software side
Practical software,right-sized.
Everything you refer is built, delivered, and supported by Julian. This page explains the work in plain language, so you can recognize it and describe it without any jargon.
- Web applications
- Client portals
- Internal dashboards
- Scheduling and booking
- Inventory and ordering
- Quoting tools
- API integrations
- Workflow automation
- Reporting
- Data migration
- Payments
- Access control

01 · Custom web apps
A product a small company hands to its customers or its staff, built for that business rather than rented from a template.
A web app is software that runs in the browser: customers or staff log in and get something done. Custom means it fits how this business actually works, instead of bending the business to fit a generic tool.
For example
- A client portal where customers book, pay, and track their jobs
- An online quoting tool that turns a two-day email thread into two minutes
- A members area for an association or training business
"Our customers keep calling to ask where things are."

02 · Internal tools
The unglamorous system that replaces a spreadsheet a team is tired of emailing around.
An internal tool is used by the team, not the public. It replaces fragile spreadsheets and manual steps with a simple, reliable system that has the right screens for the right people.
For example
- Job scheduling and dispatch for a field-service team
- Inventory and ordering in one place instead of three
- A dashboard that shows the owner the numbers they check every morning
"Only Maria knows how that spreadsheet works."

03 · Integrations and automation
Connecting the tools a company already pays for, so the work stops living in five inboxes.
Most small businesses already pay for good tools that don't talk to each other. An integration moves data between them automatically, so nobody retypes the same thing twice.
For example
- New online orders flowing straight into accounting
- Form submissions creating tasks and customer records automatically
- Weekly reports assembled and sent without anyone exporting anything
"Every Friday someone exports it and imports it over there."
How a project runs
What your client can expect, step by step.
Your name is on the introduction, so it matters how the work is run. Every project follows the same shape.
01
Scoping call
Julian and the owner talk through the problem, with you on the call. No jargon. The goal is to understand the work, not to sell.
02
Written proposal
Scope, price, timeline, what is included and what is not, and who owns the code. All in writing before anyone commits.
03
Build in short steps
Work is shown early and often, so the owner sees progress and can steer before anything is finished.
04
Handover and support
Documentation, training for the team, and an agreed support arrangement. Good first projects lead to follow-on work.
Selected work
Case studies are coming, and they will be real.
The first case study is published when a client agrees to be named. This site will not invent a project, show a screenshot of someone else’s product, or claim a result that cannot be defended.
Grow together, Earn together
Know a business that needs this?
Tell Julian what you want to make together. You do not need clients to refer. It takes about ten minutes.