Rachel Seguin — Implementation Manager

I fix the work nobody owns.

I work at the part of the job where everyone assumes someone else is handling it. That's usually where the problems are.

I take the thing nobody has fully defined yet and turn it into a plan someone can actually work from.

I keep execution moving across teams, time zones, and vendors - so it doesn't stall every time someone's unavailable or unclear.

I build the documentation and workflows that still exist six months later, when the original context is gone.

Execution proof.

Examples where the focus was making delivery more reliable, accountable, and calm under pressure.

MONA

Creative operations and delivery

Reduced avoidable rework and clarified accountability across North America, Hong Kong, and New Zealand during scaling and team contraction.

Owned cross-functional execution across community, production, and product workflows. Built repeatable launch and handoff processes that improved consistency without unnecessary process weight.

Tools: Notion, Airtable, Slack, Discord, Figma, Zoom, X/Twitter, Bluesky, Instagram

Proof

Community operations

Created a faster support baseline by implementing a trained FAQ workflow that handled roughly half of incoming repetitive queries.

Designed a cleaner triage flow for distributed teams across North America, Europe, and APAC while reducing manual support overhead.

Tools: Notion, Slack, Linear, Zendesk, Zoom, Discord

Professional Association

Implementation and operations

Removed continuity risk by securing independent backups, admin rights, and clearer accountability around website and domain operations.

Identified vendor dependency and fragmented ownership as operational risk, then added SLA structure with developer support to improve resilience and oversight.

Tools: Microsoft 365, Monday.com, GitHub, Zoom

Practical builds, framed as implementation.

These are not a pivot into portfolio mode. They show how I approach coordination friction, workflow design, and getting useful systems into real use quickly.

BBQ Potluck Coordinator

Live

Problem

Potluck planning kept breaking down into duplicate dishes, missing essentials, and too much coordination in chat.

Build

Built a mobile-first app where hosts publish one potluck page and guests update contributions from a shared link, with no account creation.

Result

Shifted planning to one live source of truth, reducing back-and-forth and making updates fast and reliable.

Stack: Next.js, React, TypeScript, Tailwind CSS, Supabase

Interactive demo link coming soon.

Kitchen Assistant Bot

Pilot

Problem

Meal planning was inconsistent because pantry visibility was incomplete and decisions were split across notes and chat.

Build

Built a Telegram-based assistant for meal decisions, inventory tracking, shopping flow, and recipe retrieval.

Refining

Tuning first-response quality, onboarding flow, and inventory assumptions before wider rollout.

Stack: Python, Telegram bot runtime, PostgreSQL, local LLM workflow

Interactive demo link coming soon.

Hands-on implementation roles.

The strongest fit is a role where execution ownership, systems clarity, and accountability are part of the core job.

I want end-to-end ownership — from problem framing through execution and continuity, not just one slice of it.

I do my best work in live operating environments where improving systems and coordination has visible, practical impact.

I'm looking for teams that value clarity, measurable progress, and low-friction execution over internal theatre.