For digital agencies
Your overflow WordPress team.
When launches overlap, we build, fix, and look after your clients’ sites in your stack, under your direction. Your client stays yours.
Sample pull request. The agency and client are fictional.
What we take on.
One job or a steady stream. Scoped in writing before anything starts.
- Builds from your designsFigma or Sketch to a custom WordPress theme, template by template, matched to the design.
- Features and pluginsCustom functionality, custom blocks, and ACF Pro layouts for sites you already run.
- IntegrationsMembership systems, CRMs, events, donations, courses, and email marketing.
- MigrationsMoves between hosts or platforms, with a URL map and redirects.
- Accessibility fixesAudit findings fixed in the code and retested by keyboard and screen reader.
- Speed workCore Web Vitals and Lighthouse scores, fixed at the template and the asset.
- Security and recoveryFirewalls, Cloudflare, access reviews, and restoring a compromised site.
- Care for launched sitesMonthly updates, small changes, and daily checks, so your team stays on new work.
- Public-sector bidsAccessibility testing, conformance reports, and teaming when your client is a government.
In your stack.
We follow your conventions, your linting, and your review process.
- WordPress Custom themesACF ProSecure Custom FieldsTimber and TwigMultisite
- Front end HTMLCSS and SassJavaScriptAstro
- Back end PHPComposerLaravelWP-CLIREST APIs
- Plugins we know well The Events CalendarGiveWPLearnDashGravity FormsPolylangWordfencePublishPress
- Hosting and delivery KinstaCloudflareGitPull requests
- Also Drupal work, scoped first
How a job runs.
Acceptance criteria agreed before we touch the repository, and enough evidence for your lead to decide it is ready.
- Step 1BriefYou share the brief, the repository, the design, the hosting constraints, and the deadline. We flag missing inputs before anything starts.
- Step 2ScopeA fixed scope and price, or reserved capacity, agreed in writing, with acceptance criteria your lead signs off.
- Step 3BuildIn your repository and your conventions, on a branch. Changes to your deployment process are agreed separately.
- Step 4Hand offA pull request with notes: what changed, what was tested and how, known limits, and release steps. Your lead approves the release.
Your client stays yours.
- Your agencyStrategy, creative direction, client communication, content approval, and acceptance of the work.
- LFWThe agreed development, testing, documentation, and fixing anything within the delivery scope.
- In writingWhite-label or credited, an NDA, repository access, who approves what, and client contact rules. We contact your client only when you authorize it.
Everything we can do for your clients.
Every capability is available under your name, from running a site month to month to accessibility work for a public-sector client.
- Run the website Unlimited small changes, updates every month, continuous improvement, and more.
- Build and rebuild Custom WordPress themes, rebuilds and migrations, plugins and custom features, and more.
- Connect your systems Membership and CRM, events and registration, donations and payments, and more.
- Accessibility Assessments, remediation, conformance reports, and more.
- Security Firewall and Cloudflare, access reviews, activity logging, and more.
- Speed and search Speed work, search visibility, AI search, and more.
- Contracts and procurement RFP responses, teaming, published agreements, and more.
- All capabilities The full list, in one place.
Who you work with
Agency work, before LFW.
Leland Fiegel Founder. Web developer at The Jake Group, Targeted Victory, and Berman and Company, building client sites and campaign pages on agency deadlines. Later a senior WordPress developer at Liquid Web and on the in-house team behind more than 100 WordPress sites at Stand Together.
Leland’s prior work.
About LFWQuestions.
Do you work white-label?
Yes, or credited, whichever you prefer. The terms, an NDA, and the rules for contacting your client are settled in writing before the work starts.
Do you bill hourly?
No. Each job is a fixed scope and price, or reserved capacity agreed in advance, so your margin is known before the work starts.
Can you work on an older site?
Yes, after reviewing the stack, access, and deployment process. We flag unsupported dependencies before quoting. Modernization is its own scope when it is needed.
How fast can you start?
It depends on the brief and our current capacity. We tell you what can be delivered and when before you commit. There is no automatic rush turnaround.
Who owns the code?
Your client or your agency, as your contract with your client says. We keep no rights to reuse your client’s work, and nothing we build needs LFW to keep running.
What hours do you work?
Monday to Friday, 9 a.m. to 5 p.m. Eastern (6 a.m. to 2 p.m. Pacific), excluding federal holidays. We generally do not offer after-hours or on-call coverage unless it is negotiated separately.
Send us the brief and the deadline.
Or book twenty minutes, developer to developer, to talk through the repository and what your team needs.