Sounds like a typical bit of customisation - a fairly simple custom entity, a couple of status reasons to track progress (draft > requested > in progress > sent) and some views so people can see what is going on (eg backoffice staff can see all records in "requested" status that they need to deal with, and when they update the status they go from this list to another. Field person can check status without having to call anyone. Slightly more work if you want them to choose from a specific list of brochures rather than just type a big text field of requirements (use another custom entity for brochures with a N:N relationship to the request record). If lots of options, use data import to create these records rather than doing them by hand Overall a couple of hours of point-and click customisation, maximum.
↧