Custom systems
A system built for your grant.
Built for your organization and run by LFW, at a fixed fee for each deliverable.
What you get.
For organizations whose funding or solicitation calls for development, such as federal grant recipients and agencies whose RFP excludes off-the-shelf software.
-
Built for you
A system designed around your program, your users and the requirements in your award or solicitation.
-
A dedicated U.S. environment
Your system runs in its own environment, hosted and staffed in the United States.
-
Operated by LFW
Hosting, monitoring, backups, security patches, support and releases are ours to run.
-
Fixed fees, never hourly
Each defined deliverable has one fee, agreed in writing before the work starts.
Who owns what.
Written into the agreement before the work starts.
-
LFW keeps its code
The code stays LFW’s, so we can keep improving it and support it for as long as you use it.
-
You get a license for good
A perpetual, irrevocable, royalty-free license to use, modify and operate the system.
-
You own your data
Your records, content and user accounts belong to your organization at all times.
-
A full copy on exit
If you leave, you receive a complete export of your data and a copy of the source code.
For federal awards, the government keeps its own license to work developed under the award, as 2 CFR 200.315 provides. The agreement acknowledges it.
How a project runs.
Four steps, each ending with something you can check.
- Step 1 Discovery We read your award or solicitation, interview the people who will use the system and write down what it must do. A written scope and a fee for each deliverable
- Step 2 Build in milestones Work arrives in stages. Each milestone has acceptance criteria in writing, and you approve it before the next one starts. A working release at every milestone
- Step 3 Test The system is tested against WCAG 2.2 AA, and an independent party tests its security. The accessibility and security test reports
- Step 4 Pilot and operations A small group uses the system first. After the pilot, LFW operates it and releases improvements on a schedule. A running system and a support contact
Web, iPhone and Android.
The people you serve use the phone they already have.
- Installable web app by default It works on any phone from one address, installs to the home screen and leaves no app store record.
- Native iPhone and Android when needed When the program needs them, native apps are published under your own Apple and Google developer accounts.
- Built for your program One code base per platform, written for your program, under the same ownership terms as the rest of the system.
Made for funded projects.
Where a grant pays for the work, the paperwork matters as much as the software.
- Itemized by grant year Fees are listed per grant year, one-time costs apart from recurring ones, so they map to your budget.
- Procurement-ready documentation Scope, acceptance criteria, rights terms and security practices are written to be attached to a proposal or file.
- No work offshore The people who build and operate your system, and the systems that hold your data, are in the United States.
If LFW’s standard software already does it, that is faster and costs less.
A custom system is for work LFW’s standard software does not cover, or for funding that excludes ready-made software. We will tell you in discovery if LFW already does what you need.
Who builds it.
LFW is led by Leland Fiegel, who has built for the web since 2007. He was WordPress administrator for Arlington County Government in 2017, as a contractor, responsible for more than 40 public-facing websites: operations, updates and security patches.
Read more about LelandQuestions.
What does a custom system cost?
After discovery we quote one fixed fee for each defined deliverable, plus a recurring fee for hosting, operations and support. Both are itemized by year. Scope changes are quoted for your approval before any work starts. We do not bill hourly.
How long does it take?
It depends on scope, and the written scope gives a date for every milestone. A first working release usually comes well before the pilot. If your funding has a calendar, we plan backward from it.
Who owns what?
LFW keeps its code. You hold a perpetual, irrevocable, royalty-free license to use, modify and operate the system, and you own your data. For federal awards, the government’s license under 2 CFR 200.315 applies to work developed under the award, and we acknowledge it in the agreement.
What happens if we leave?
You receive a complete export of your data and a copy of the source code. The license continues, so you or another vendor can keep running the system.
How do you handle security and accessibility?
The system is tested against WCAG 2.2 AA, and an independent party tests its security. Both reports go to you. It runs in a dedicated U.S. environment with monitoring, backups and security patches handled by LFW.
Our security practices and policiesCan it connect to our existing systems?
Usually. We confirm during discovery what each system offers, such as an API or scheduled file exchange, and the written scope lists every connection. If a system offers no way to connect, we say so before you approve anything.
Do you work with grant timelines?
Yes. Fees are itemized by grant year, milestones are dated to your award period, and the documentation is written for reviewers and auditors.
What if we only need standard features?
Use LFW’s standard software. It is faster and costs less, and it is the better choice whenever your funding allows it.
See how LFW worksSend us your award or solicitation.
We read it and reply with a written scope and quote within one business day.