Access a service
Member portals, applications, registrations, and account areas. Give people access to their own information, with appropriate permissions for staff.
New application builds
Custom web applications.
A portal for your members. A directory that helps people find the right help. A tool that replaces a spreadsheet and a chain of emails. We build software around the work your organization needs to do.
Start with an idea. You do not need an existing website or a retainer.
What should people be able to do?
Find the right match
Directories, resource libraries, and matching tools. Use structured information, useful filters, and criteria your team can understand and maintain.
Move work forward
Booking, approvals, reporting, and internal workflows. Connect the systems you already use and make the next action clear.
Independent products, live today.
TransitTab and DomainMantis were built by Leland Fiegel as independent products. These are examples of our founder’s application work, not LFW client commissions.
TransitTab
A transit application that brings station search, live arrivals, and transfer-aware trip planning together. Find a stop, follow the next arrivals, and share a route.
Python / FastAPI · JavaScript
Explore TransitTabDomainMantis
Turn an idea into domain-name candidates. Explore prefixes, suffixes, and extensions, then filter and verify options before heading to a registrar.
Python / FastAPI · JavaScript
Explore DomainMantisAlso running on LFW.com.
We build and operate applications for LFW itself. These are our own working products, not client commissions; the Client Portal preview uses fictional demonstration data.
Website auditor
A request starts automated checks, organizes the findings, and produces a report. Background jobs keep the longer checks out of the visitor’s way.
See a sample reportBooking system
Visitors choose an available appointment. The application handles availability, calendar integration, and the booking workflow.
Explore bookingClient Portal
Clients submit requests, follow conversations, and review website information in an account area with controlled access.
Tour the portalThe work comes first. The stack follows.
We work with PHP and Laravel, Python, Node.js, React, and WordPress. These tools serve different purposes and can work together. We recommend an approach based on the application, your existing systems, and who will maintain it.
Application foundations
Laravel is a PHP framework for building applications with accounts, data, permissions, and background jobs. Node.js and Python are other options for server-side services and integrations.
Interactive interfaces
React can support interfaces with complex interactions or changing data. Simpler screens may need much less JavaScript. We choose what makes the experience useful and maintainable.
Publishing and content
WordPress can be a strong fit when publishing is central to the application. A separate application can also sit alongside a WordPress site; shared sign-in is a requirement to plan, not an assumption.
From an idea to a working application.
-
Define
Start with the work people need to do.
We review the users, workflow, data, and connections. Together, we choose a useful first release and agree its scope, price, and acceptance criteria. If discovery needs its own project, we quote that first.
-
Shape
Try the important interactions early.
A prototype makes the proposal tangible. Your team can test the main journey and resolve questions before we build the full application.
-
Build
See progress, test real scenarios.
We build in reviewable stages and check permissions, accessibility, error handling, and performance. Your team tests the agreed workflows before approving launch.
-
Launch
Leave with the application and a plan.
We arrange deployment, documentation, and a practical handoff. The agreement identifies ownership, licenses, access, and any separately priced support after launch.
Keep the running costs in view.
The development quote and the cost of running the application are separate. Hosting, email delivery, paid software, and any AI services need their own approved accounts and budgets. We explain the dependencies before you commit; unlimited provider usage is not included in a build fee.
AI is optional, not a prerequisite. Structured fields, rules, and search may solve the problem without it. If AI adds value, we define its job, spending controls, and what continues to work when it is unavailable.
After launch, we can agree a support plan for the application. If your existing website needs ongoing care, explore the Web Operations Retainer. A new application receives its own project scope and quote.
Tell us what people need to accomplish.
Bring the idea, the recurring frustration, or the process you want to improve. We will help you work out a practical first version.