A software development partner with a written release
HED Creative partners with companies when a standard product cannot carry the workflow. You get a scoped release, code that transfers to you, and a handover someone internal can operate. A retainer is optional. A package menu is not how the work is sold.
Who it is for
A partner is useful when someone inside the company can decide, and the workflow can be described.
A fit
- Established companies whose process does not fit the ERP screens they already pay for
- Teams that want the repository and documentation after the project
- Operators who need English as the working language, with delivery from Berlin and Ankara
- Buyers who will define a first release instead of a platform vision
Not a fit
- A pitch with no user and no source of data
- A fixed price for “Salesforce, but cheaper”
- Clients who want the source to remain only at the agency
- Helpdesk, device support and overnight infrastructure cover
A premium project, not piecework
A partnership is not an hourly shop. It is a closed project or a monthly retainer. Below that — one banner, one theme, a ticket with no owner — we decline. The fee follows capacity and delivery.
Why the last software project stalled
The stack was not the failure. The release was never defined, and ownership was never written down.
The process was bent to the tool
People fill fields nobody reads and keep the real record in a spreadsheet.
Integrations stay “phase two”
ERP, CRM and the new screen do not share a record. The order is typed twice.
Ownership is vague
After go-live the repository sits with the vendor. Changing partner means rebuilding.
Nobody owns care
The release ships. Defects and small changes have no named month.
How the partnership works
Release one finishes a described workflow. Roles, data and integrations are in the proposal. Handover includes the repository, the environment and a short operating note. If personal data is processed for you, that processing is agreed before launch. A monthly retainer can follow. It does not hold the code.
A written release
Screens, exclusions, date, fee. Changes are change requests.
You own the code
The agreed source moves to you after payment. It is not collateral in the agency account.
A handover someone can run
Access, known limits, and the name of the internal owner.
An optional retainer
Defects, small extensions, care. Priority written each month.
From workflow to handover
We do not start from a technology list. We start from the workflow and the first release.
Workflow
How the work happens now, which system stays, which one is replaced.
Proposal
Release, fee, ownership. Without those, work does not start.
Build
Reviewable slices. Acceptance means the workflow ends in the software.
Handover
Access and a note. A retainer only if you commission it.
What can be public
Custom operational software is rarely public. The examples are published systems with a clear next step, not claimed ERP replacements.
A project or a retainer
There is no shelf of software modules with package prices. The first engagement is a project with handover. After that, a monthly retainer can cover defects and small extensions. Both state what is not included. You keep the code either way.
Project
One release, one fee, one handover, ownership transferred.
Retainer
Monthly care with a written priority. No unlimited bucket, and no code held back.
Questions before you enquire
Do you work fixed price?
Yes, when the workflow can be described. If it cannot, there is a paid clarification and then a fixed price on the release. There is no fixed price on an undescribed product.
Who owns the software?
You do. The agreed code, the repository and access are handed over.
Can you take over existing software?
If the repository, the environment and an internal owner exist, yes, as a diagnosis first. Without access we do not promise a rescue.
Is a retainer required after launch?
No. A clean handover is the default. A retainer is right when the workflow keeps changing.
Where is the team?
Berlin and Ankara. The working language of this page is English. German and Turkish projects run in those languages, not as a translated copy of this one.
Before the conversation
One counterpart replaces scattered invoices. Access and measurement sit in the agreement.
Process
First the current stack and the priority. Then a project or a retainer. A mixed scope is not written.
Ownership
Code, accounts and content stay with you. The partner gets access, not the title.
Reporting
A monthly note: work done, work next, risk. An hour log alone is not a report.
Measurement
Which delivery or which enquiry counts as success is written at the start.
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
What fails today, which system stays, and who decides internally.
We send the release, the fee and the ownership terms in writing. An undescribed product is not priced.
Related pages
Partnership, a single web app and custom software are different doors.
Related reading
Describe the workflow
What fails today, which system stays, and who decides internally.