Web app development for a workflow, not a concept
HED Creative builds web applications when email and spreadsheets no longer carry the work. The first release finishes one workflow. Scope, code ownership and handover are written. There is no app package.
Who it is for
An application is justified when the same decision is late every day.
A fit
- Quotes, orders or service cases disappearing into inboxes
- Dealers, clients or field teams who need their own login
- An ERP or CRM that exists, with no screen in front of it
- Operators who will keep release one small and extend it monthly
Not a fit
- A product no user has touched, scoped as “everything”
- Consumer store apps, games or social networks
- Clients who want the code to stay locked at the agency
- A brochure website described as an application
Why the work is still in a spreadsheet
The issue is not a missing brand of software. The same figure lives in three places and none of them agree.
Every quote is a copy
Price, discount and version have no history. Sales hunts for the last file.
The dealer orders into a void
A screenshot is typed into stock. The error shows up on the invoice.
Management sees the queue too late
Open work is merged at month end. The decision arrives after the incident.
The system lives with one person
The previous developer leaves with the repository and the server password.
What HED Creative builds
Release one closes a single workflow: quote, order, enquiry or field report. Roles, screens and the link to the system you already run are in the proposal. Handover includes the code, access and a short operating note.
One workflow, one release
Not a platform story. If someone finishes the job in it daily, the release is the right size.
Roles
Sales, operations and dealers see the same records, not the same fields.
Integration
ERP, CRM or finance through a described API. Double entry is not a success.
You own the code
Repository, server and admin access are handed over. The app is not held in the agency account.
From workflow to release
Discovery is as long as the screen list. We do not price “digital transformation” without a process.
The workflow
Who decides what, from which data. The spreadsheet or ERP is named.
A written release
Screens, roles, exclusions, date, fee. Anything outside is a change.
Build
A usable slice at short intervals. The test is whether the workflow ends.
Handover
Access, a short note, known limits. A retainer is a separate monthly scope.
What can be shown
Internal applications are not published without permission. The examples below are public enquiry and catalogue flows, not claimed internal systems.
A project, then a retainer
We do not sell versioned app packages. Release one is a project with handover and ownership. Later screens are a change request or a monthly development retainer. In both cases the code is yours.
Project
Release one: screens, date, fee. Then handover.
Monthly development
Small screens, defects, integration. Priority written each month. No unlimited bundle.
Questions before you enquire
Do you customise an off-the-shelf product?
If an existing system can carry the workflow, we say so. If it cannot, we build the screen for your process. There is no hidden app package.
Who owns the code?
The agreed code is handed over with the repository and server access. The application keeps running if the engagement ends.
How long is release one?
A single workflow, with fast decisions, sits between several weeks and a few months. ERP links and many roles extend it. The date is in the proposal.
Is a native mobile app included?
The first build is a web application in the browser. A phone-ready screen covers most field work. A store app is separate scope.
Is a retainer mandatory?
No. Handover is a usable release. The retainer is for new work and care, not a condition of the software staying yours.
Written scope
Pages, timing and fee are written down.
A process you can follow
Each step has an outcome you can check at the next conversation.
TR/DE/EN market language
Buyers in Turkey, Germany and international markets are addressed in their own language.
Describe the workflow
Who uses it, where the work lives today, and which system already exists. That becomes release one.
We ask for the missing decision, then send screens and fee in writing. Work a website can do is not sold as an app.
Related pages
An application sits next to portals, integration and a longer partnership.
Related reading
Describe the workflow
Who uses it, where the work lives today, and which system already exists. That becomes release one.