Lindsay LaShell

Systems and AI implementation. Hand me a spec and I can build it. Hand me a mess and I will tell you where we should start the clean up.

$100/hour, no minimum · Available now · Happy to subcontract or work under your brand

Lindsay LaShell, smiling, seated in a leather chair. Photo by Myra Thomas, Denver, 2025.

Two decades of working closely with underestimated founders and nonprofit leaders has taught me to diagnose opportunities quickly, prioritize them for impact, and then design and build the systems that make them real.

For the last two years I have been doing that for myself and my clients in deep collaboration with Claude Chat, CoWork, and Code.

How I Work

I build what you designed.

If you’ve done the strategy and the feasibility work, I can turn it into working systems. I’ll build agents and instruction sets, wired to the tools the client actually uses, with the guardrails and failure handling that keep them working when the model returns something unexpected. Then I document it and train whoever is going to run it.

Most implementations fail in the gap between a design and the client’s real systems, where the data is not shaped the way the plan assumed, or a tool doesn’t deliver it as expected. That gap is where I am most useful.

I build for durability and functionality.

I am completely platform agnostic when it comes to client tools. If it makes sense to migrate, or if it makes sense to stay, I’m going to advocate for the simplest and most robust solution that fits within client budget and capabilities.

I build things other people can run.

Documentation, playbooks, and training are part of the job, not an upsell. I have a background in teaching and curriculum development and am committed to making technical systems that work for humans.

I’m a business services pro.

Give me an ambiguous scope and I will make the calls that are mine and surface only the ones that are yours. After years of running my own service-based business, you can be confident that your client relationship is not at risk while I am on the job.

Real Business Problems I Solve

Processes I automate

  • Lead capture to CRM to follow-up, where the routing actually fires
  • Customer and member onboarding
  • Recurring content production
  • The monthly report someone rebuilds by hand
  • Purchase to fulfillment to access
  • Inbox triage and drafting
  • Personalized outreach at volume
  • Event registration, reminders, and follow-up
  • Subscription upgrades, downgrades, and comps
  • Internal handoffs that currently live in Slack
  • Intake forms and everything downstream of them

Messes I clean up

  • A strategy or roadmap that was approved and never built
  • “Our forms stopped working and nobody noticed”
  • A brand that looks different on every asset
  • Two systems with contradictory data
  • A half-finished platform migration
  • Software or systems implemented but not adopted
  • Emails that look broken on phones
  • Automations built by someone who left
  • Essential processes that only exist in the leader’s head
  • Neglected or outdated accounting processes
  • Five subscriptions doing two jobs, and three more tools not doing any
  • Policies that get written during the crisis and never got implemented
  • AI output that is generic, boring, or over-reliant on em dashes

Tools

Kajabi · Brevo · Substack · HubSpot · Make · Stripe · Netlify · GitHub · Cloudflare · Namecheap · WordPress · Webflow · Canva · Circle · Mighty Networks · Skool · Luma · Asana · Trello · Notion · Slack · Xero · Google Workspace · Google Sites · Google Apps Script · Zoom · Loom · Fathom · LinkedIn Sales Navigator · Claude (Chat, CoWork and Code) · ChatGPT · NotebookLM

New platforms are not a problem, I’m fluent in support chatbot, Google search, and lots of other information sources.

Case Studies

01 · Build the whole thing

Buffalo Collective, 2025 to present. My own company, so I can show you all of it.

I needed a website, an email system, a newsletter, payments, and a community platform, with no budget and no team, so I decided to try my hand at vibecoding.

The site is Claude-written HTML, CSS, and vanilla JavaScript, deployed from GitHub to Netlify, with serverless functions routing every form into Brevo and Fathom for analytics. The site is registered at Namecheap and has SPF, DKIM, and DMARC records so the email sends are trusted. Beyond the site design, I built the newsletter template system from scratch: type, palette, modular components, and a color convention that signals what kind of send you are getting before you read a word, then built the automations and workflows in Brevo.

When all that was done, I found the entire effort so rewarding and effective that I wanted to pass it forward. I thought it was especially important to highlight the preparation and spec work that is needed to create a finished website that is stable and robust enough to accept significant edits and updates. I turned the method into an online course that teaches non-technical people to do the same thing with Claude.

I built a durable and high quality marketing platform for a bootstrapped new business.

02 · Set them up for success

One example of many: An AI agent is only as good as the standard behind it, and almost nobody has written theirs down.

A nonprofit entrepreneurship ecosystem organization. 2022, and again in 2025.

They had a rotating cast of people running social media. Every handoff meant a new interpretation of scope and tone, so the brand drifted.

With Claude, I provided the standard that stopped it. Starting with dozens of hours of transcripts from the founder’s podcast, I created a voice guide that turned the founder’s natural speech into four named pillars. These were mapped to context, with four audience segments and explicit rules for what to avoid with each, and substitution pairs, so it is usable rather than aspirational: instead of “utilize,” try “use.”

Then we designed the workflow that runs on top of it: A documented process from objectives to scheduled posts, with an AI prompt built into the procedure for generating a 90 day calendar, including what to do when the model returns an incomplete answer. Approval is split in two: the communications team signs off on execution, the executive director reviews concepts only, and the document says in writing what she does not review.

I created a social media system that allows any team member to execute for consistency and connection, and I reduced the founder’s administrative task list at the same time.

03 · Fix the plumbing

A regional garden design and education business. 2026.

The client needed a full newsletter overhaul. They wanted off MailChimp, because it was expensive, and it did not fit their values, but they also needed a new strategy for making the most of a list that had gotten very inconsistent attention over the past year.

I started with an audit of their existing database and tag structure, then constructed the new field and tagging strategy in tandem with the new messaging strategy. A migration is a rare chance to fix what is underneath, so I rebuilt the data model on the way through: first touch preserved, most recent offer overwritten, data we needed pushed forward, and what we didn’t was shed along the way.

Aside from the MailChimp to Brevo transition, this new build required configuration of Make scenarios to accurately pass customer information from Kajabi to Brevo, so I built the integration on per-form webhooks and wired the whole path with error handling: course platform to automation layer to email to payments. I set up authentication and monitoring on the domain.

I built what they asked for, and upgraded the strategy and infrastructure while I was there.

If you have a client with a system that needs building, fixing, or documenting, send me the scope.

There is no minimum, so a two hour fix is a perfectly good place to start. I am comfortable working behind your brand or in front of it, whichever serves the engagement.

lindsay@open-lines.co