The right file. In the right place.
A shared folder stores files. A Rosfish request tells your client which files you actually need and shows you which ones have arrived.
Create your first request →Give every asset a clear instruction.
Name the file and explain how it will be used. A client who understands the purpose can make a better choice than someone asked to send ‘the assets.’
- Logo: use a PNG or package vector originals in a ZIP
- Team photos: provide the approved images
- Brand guidelines: upload the current PDF
- Website copy: attach a DOCX or answer in a long-text item
Collect context alongside files.
Add a text question next to an upload for credits, usage notes, or missing details. Combine a file item with a URL when a live reference helps. Rosfish supports six response types in the same request, so the explanation does not get separated from the asset.
Save now. Replace when needed.
The client can return to the request link and upload a replacement. The current file is shown beside the item, and the previous file is removed from active storage. Download files you need to retain in your own project archive.
Keep large deliveries in their own workflow.
The upload limit is 10 MB per file. For large video or photo libraries, use a URL item to collect a link from the client’s existing storage service and verify its permissions. Rosfish keeps the request and its answer organized without pretending to replace a large media archive.
A clear list.
A little less friction.
Your client sees the business requesting information, the items still needed, and the progress they’ve made. Responses save as they work. No client account required.
Find a starting template ↗Website launch
materials
A few things we need to bring your new site to life.
Get the inputs.
Get on with the work.
Create your first request free. No credit card. No client login.