Follow-on engagement to the SEO/performance intro project. The goal is to evaluate and begin migrating iroco.com off Drupal 10 onto a faster, cheaper Astro + Cloudflare stack with a narrow custom product admin/API backend.
Because iroco is a custom B2B catalogue + RFQ platform (not a simple webshop), this is structured as a two-phase engagement: a fixed-price discovery + catalogue/data/backend proof slice first, then a workflow rebuild that is estimated only once the client has defined the target workflows.
Instead of starting with a general-purpose CMS such as Strapi or Sanity, Phase 1 will prototype a small custom product admin/API backend. The goal is to support Iroco’s real operational needs: importing/uploading products, editing product data, managing product images/files, seeing users/members, and feeding Astro with clean catalogue data. This keeps the backend flexible for later workflow changes without forcing the site into a generic CMS model too early.
Data migration is small — 13,711 products with clean attributes/prices is a couple of days of work. The real cost driver is rebuilding behaviour: the RFQ/project engine, multi-currency + discounts, search/facets, import tooling, member roles, and transactional email.
Many of these workflows should be redefined by the client, not ported 1:1. They can't be priced responsibly until they're defined — so the workflow rebuild is deliberately separated into Phase 2.
Fixed price · ~3 weeks. This is the part that needs no client redefinition.