Client delivery
One directory. Six CSV files delivered.
A directory held useful information that needed to be organised outside the original site. The engagement delivered six structured CSV files.
The need
Make information from a directory usable in files, with an agreed structure for reviewing and reusing the data.
The delivery
The directory information was delivered to the client in six CSV files. The client's identity, the original files and their contents remain private.
Explore the format
The preview illustrates how a delivery can be organised. File names, columns and records are fictional examples, not the original client files.
Starting point
A web directoryDelivery preview
| Organisation | Category | Location |
|---|---|---|
| Example Studio | Design | North district |
| Sample Workshop | Craft | Central district |
| Demo Collective | Consulting | West district |
Illustrative delivery format — fictional data.
A service for a similar need
A clear scope. A direct conversation.
Define the result
Show me the source, the current process or the product idea. We clarify what a useful delivery should let you do.
Agree the scope
We set the deliverables, constraints, price and handover before work starts.
Review along the way
An appropriate checkpoint lets you review a sample, a workflow or an application as it takes shape.
Receive and use
You receive the agreed files or software, with the explanation and handover defined for your project.
A few things to know before we talk.
What should I send to get started?
A short description of the result you want is enough for the first conversation. Include a source URL, a sample file or a description of your current process when available. A deadline is useful if you have one.
How is the price defined?
The price follows the agreed scope: what must be delivered, the constraints and the required handover. We discuss those before work begins; there is no fixed price for every project.
Can you work on something that already exists?
Yes. I can review an existing application or workflow, identify the relevant constraints and propose a focused intervention.
Can a delivery run on a recurring basis?
Yes, when that is part of the scope. A one-off file delivery and an ongoing automation have different needs; we agree the frequency, running environment and upkeep together.
Is maintenance included?
The delivery and handover are defined in the scope. Ongoing maintenance, support and later changes are agreed separately.
What would make your work easier?
Send me the source, the task or the idea. We can start with the outcome you need and clarify the rest together.
Remote collaboration · Direct contact with Elvan · Scope agreed before work starts
WhatsApp opens an editable message. Nothing is sent until you choose to send it.
Find me on LinkedIn