Fidelock logbook
Fidelock builders in daylight, atlas poets after curfew.
Between pager alerts and redeye landings we keep a shoebox of card rumors, lounge sketches, and datapoints like pressed flowers; this page is the letter tucked inside the atlas. In daylight we speak in runbooks and timelines. After hours we unfold paper, smooth out creases, and retell the same scenes with the patience of friends passing notes across a long flight.
Tracing moonlit work across three cities.
Grad-school nights in Vancouver meant empty residence hallways, rain against the bus shelter, and a spreadsheet glowing like a lantern. We logged welcome offers for friends, tinted every approval like a train timetable taped above a tiny desk, and realized a perk could double as a compass point. Back then we did not call it a product—just a nightlight—but that glow gave us enough courage to keep mapping.
Days belonged to French cafés and enterprise code; evenings were saved for bilingual DP relays. Screenshots from English forums were annotated line by line for Chinese chats, and 2 a.m. reminders from Chinese groups became English footnotes. Friends called us a bridge, yet the bridge felt narrow, built stone by stone through patience. That year Perkmap learned to respect how each community breathes.
Clients sign off, we stay behind. There is red light from the runway, warm light on our screens, and commit messages that read like postcards. Someone tends scrapers, someone narrates a lounge comeback, someone remote-checks punctuation—it is our second shift. Slowly Perkmap turns into Fidelock’s night logbook, documenting care that daytime never sees.
Opening field notes so every reminder feels human.
Precision survives, but we give every card a voice so it travels beside you instead of sitting in a cell. We ask if the issuer reminder carried a particular tone and whether the subway to the airport had buskers, because those textures influence how a perk feels. Each entry behaves like a chapter heading waiting to be read aloud.
DPs arrive like postcards. We log provenance, describe the weather, and slide each story behind a glassine sleeve before pinning it to the atlas wall. Long-haul whispers, hold music, and the look on someone’s face when a perk clears are all cataloged. Someday we hope to host an exhibit that is nothing but footnotes.
There is no venture clock. Ship dates follow family dinners and redeyes, which keeps releases sounding like journal entries rather than drops. Sometimes bedtime runs late and we log an apology in the changelog; sometimes a typo fix happens while queueing at check-in and the observation becomes a comment. Moving slowly confirms Perkmap should keep a human temperature.
Giving the map legend a green spine so structure stays warm.
Issuer rules, upgrade ladders, and community folklore share a single compare stack, letting you narrate your own line through the map. Traveler notes sit beside schema fields, calling out which clause hides a phone promise. Tuning the compass means trusting both data and intuition, like sharing a lamp in a rainy terminal.
Room sketches, family tags, lounge trust scores, and reader letters live together. We ask if kids can nap in the lobby, if the pool became a meeting hall, and the names of staff members who made the stay softer. These details become constellations along the page edges.
Serialized essays cover card ladders, lounge surprises, and near-misses we refuse to hide. Each draft gets at least two verbal run-throughs so the breathing of the storyteller remains in the copy. Perk Pulse behaves like an in-terminal radio, keeping company while you wait.
Meet the mapkeepers and note-takers behind the atlas.
Fidelock product and data teammates guard schemas, scrapers, and midnight deploys. Working in security taught them to respect evidence chains, so Perkmap inherits the same rituals. Someone will roll back a field at 3 a.m. if it misleads; someone else logs lounge temperature readings for future comparison. They also pin every bit of community feedback on a wall so the next stand-up starts close to reality.
Writers, testers, and travel friends mail back lounge gossip, detours, and warmth. They record airport announcements on their phones and turn them into margin notes, or send reviews narrated by their kids after a family trip. We call them storykeepers because they remind us that every datapoint has a person beside it.
The road ahead sits beside the letter we keep ready to send.
Slow crafting pace
Features launch only after a card or hotel collects enough story beats to deserve ink. We would rather spend weeks confirming a lounge rumor than chase a trending keyword. Backlogs stay full, but we address them at letter-writing speed so every release feels worthy of keeping.
Transparent provenance
Every DP includes its source; anything we cannot explain clearly stays out. We jot down setting, weather, and call timestamps so readers understand how we arrived at a conclusion. Transparency is our reminder: when in doubt, hit pause.
Community-first orbit
Perkmap remains a side quest. We answer mail ourselves and keep experiments within a comfortable radius. If the community asks questions, we open the doc and respond directly; if they need an in-person meetup, we bring our laptops and sit in the corner. As long as the circle stays close, we keep writing this way.
Send a datapoint, request a feature, or sip Perk Pulse like bedtime reading. We log letters in their own section, timestamp emotions, and pick a night to answer each one. The atlas grows with borrowed stories, and that keeps us aware of where we came from. If you want to add your handwriting to the blank spaces, we will keep it safe—even if replies arrive a little late with a photo of the night shift attached.
Built by Fidelock
On Fidelock’s lantern-lit desk, perks are stitched into an atlas: stack paths, expiry quirks, and quiet clauses get checked before any line earns ink. Security habits keep the page steady; the warmth comes from coaxing more value out of every offer.