Quaritalia Site Launch — Content Blockers
Overview
The Quaritalia website has been in development for over three months but cannot launch because the client has not delivered the required content assets. Hosting fees have begun accruing, creating financial urgency to resolve the blockers quickly. This is a recurring pattern worth flagging: client-side content delays on near-complete sites where hosting costs have already started.
Status
Blocked — awaiting client content delivery.
The staging site is built and ready. Asymmetric has provided page outlines and copy scaffolding. The remaining gap is entirely on the Quaritalia side.
Required Content (Outstanding)
The following assets must be delivered by Quaritalia (contact: Fede) before the site can go live:
| Asset | Notes |
|---|---|
| New photos | Replacements for current staging site images |
| Vector logo | A proper vector file (e.g., .svg, .ai, .eps) of the Quaritalia logo |
| Project examples | Specific projects they want to showcase on the site |
| Page copy | Asymmetric has written outlines; client needs to fill in the actual content |
Financial Urgency
Hosting fees began accruing after the three-month development mark. The site is effectively costing the client money without being live or generating any value. This should be used as a concrete motivator when following up with Fede.
"It has been three months, or over three months since we started working on it, so we are starting hosting fees. And if you guys are paying hosting fees, I'd like you to have the site to go, you know, actually with it."
— Karly Oykhman, Asymmetric
Action Items
- [ ] Lauren (Quarra Stone): Email Fede (Quaritalia) requesting all outstanding content; copy Karly Oykhman on the message
- [ ] Asymmetric: Once content is received, complete final build and push site live
Related Context
- This site is a subsidiary or partner project connected to the [1] engagement
- Discussed during the [2]
- The Quarra Stone main site has its own parallel update in progress (new project photos, homepage video); see [3]
General Pattern
When a client-side content dependency is blocking a near-complete deliverable and hosting costs are live, escalate with a concrete cost framing rather than a general nudge. Looping in an internal client champion (here, Lauren) to relay the message to the responsible party (Fede) can accelerate response when direct outreach has stalled.