Slide 01 · Title image
Warm bookstore interior; open book on table glowing softly with vermilion-orange light; tall bookshelves recede; orange threads curl outward to frame edges.
A catalog at the heart of Fully Booked's systems
Proposal for the AWS catalog build · [Date] · [Presenter]
Approve to start Phase 1
- AWS catalog build
- ~$27/mo recurring
- [total weeks] timeline
- Target start [target start date]
Approve Phase 1 — AWS catalog build
~$27/mo recurring · target start [target start date]
Slide 02 · The ask
Closed hardback book with vermilion-orange wax seal on the cover; calendar page floating beside it (date area blank).
Slide 03 · Today
Overhead cluttered desk; hands typing at a keyboard; four screens showing same books in different layouts (grid, list, cards, table); sticky notes and printouts piling around.
Where catalog data lives today
- Manual entry, record by record
- The same titles in different shapes across every system
- Repeated work, repeated drift
Slide 04 · What we're building
Tall central bookshelf; conveyor belt of books arriving from left (publisher boxes); same books leaving right as sealed envelopes tied with orange string.
One pipeline in. One catalog of record. Exports out.
Ingest
DataSync from your FTP server
Catalog
Cloud-managed PostgreSQL — the system of record
Exports
One folder per consumer, scheduled daily
Six publishers in. Every system out.
In · publishers
Ingram
Penguin Random House
HarperCollins
Hachette
Simon & Schuster
Macmillan
Slide 05 · Connectivity hub
Central library shelf in three-quarter perspective. Left: six small arched doorways with orange flags; books delivered through each onto conveyors. Right: four open archways leading to mini-rooms — laptop, barcode scanner, register screen, and an empty pedestal (future). Slim charcoal connector lines.
Out · systems
fullybookedonline.com .sql
Inventory management .csv
Point of sale .json
ERP / analytics / mobile / partners .parquet
Downstream systems read files from the export area — they never connect to the database.
Slide 06 · How it works
Cross-section of a book-shaped two-storey building. Left: one tall arched entry door, orange banner above. Inside, four rooms left to right — archive (books stacking), parser (silhouetted figure at table), catalog (tall central ledger with orange spine), exports (envelopes ready to leave). Right: one tall arched exit door, orange banner above.
One door in. One door out.
- Publishers push to your FTP server (you already have this).
- AWS pulls hourly into a secure archive.
- Parser and merger keep the catalog current.
- Daily exports land in each system's preferred format.
Built for SAP — when you're ready
When SAP arrives, it joins as a new export consumer. The catalog hub doesn't change. No re-architecture. No website re-deploy.
- Estimated effort to wire SAP in later: ~1–2 weeks of exporter work plus SAP-side load configuration.
- The same property protects every future consumer — analytics warehouse, mobile, partner feeds.
Slide 07 · SAP-readiness
Same hub as slide 5, zoomed toward rightmost archway. That archway is warmly spotlit in vermilion-orange light, an empty crate on a pedestal inside, three blank orange ribbon banners hanging above. Other archways recede dimly at the frame edge.
What it costs
- Build: [Build cost]
- Recurring AWS: ~$27/mo (RDS PostgreSQL + S3 + Lambdas + DataSync)
- Adding SAP or another consumer later: hours of exporter work, not a rebuild
A future VPC upgrade for a fully private database adds ~$15/mo and can be done at any later date.
Slide 08 · Cost
Top-down view of a single open accounting ledger on a wooden desk; three neat rows in vermilion-orange handwritten ink (intentionally illegible); a fountain pen resting beside.
What goes live when
Slide 09 · Timeline
Long horizontal wooden bookshelf, three equal segments divided by vertical posts. Left segment: a few books; middle: half-full mixed orientations; right: fully stocked. Each topped with a blank vermilion-orange flag.
Phase 1
Weeks 1 – [X-week]
Pipeline and catalog online. IAM-auth wiring complete. First publisher feed flowing end-to-end.
Phase 2
Weeks [X-week] – [Y-week]
All six publishers ingesting. Inventory management pulling daily from the export area.
Phase 3
Weeks [Y-week] – [Z-week]
Website cut over to the new exports. All current consumers stable. Old catalog retired.
Slide 10 · Cutover & risk
Two parallel wooden bookshelves — older weathered one on left, fresh on right. Row of books levitates between, mid-transfer. Below them, hammock-style safety net of woven vermilion-orange cord stretches between the shelves.
Safe to go live
- Staged cutover — one consumer at a time, never big-bang
- Full replay — the raw archive lets us re-process any file at any time
- Existing systems keep running until each is independently moved
What we'll need from you
- An AWS account — we configure; you own the billing identity
- IT contacts: FTP server admin and network
- Read-only access to the FTP folders for the DataSync agent
- Sign-off on the website cutover window
Slide 11 · Partnership
Two long ribbon bookmarks — one charcoal, one vermilion orange — tied together in a single neat knot at the centre; free ends trail off to opposite sides with small tassels.
Slide 12 · The decision
Same bookstore interior as slide 1, dusk light, single brass lamp glowing over the table. The book is now closed with a vermilion-orange wax seal on its cover. Orange threads still trail softly outward to the frame edges.
Ready to start
Approve Phase 1 · Target start [target start date]
We turn the ask into a signed scope of work and begin AWS account setup.