Start with a focused improvement, build a defined workflow, or ship a bounded first release. Every engagement is scoped in writing with deliverables, acceptance criteria, and a price you see before work begins. When the work is finished, three service plans keep it healthy and improving.
Which engagement fits
Each offer is defined by what it includes and what it does not. If your work fits, the starting price applies. If it does not, we say so and propose the right scope, a discovery step, or a larger program priced on the actual work.
Quickstart
Improve something that already works.
A genuinely small, repeatable improvement: adapt a tested pattern, fix a form or handoff, connect one known source to one destination, or make a targeted improvement to an existing application.
Suitable for
Adapting an existing, tested pattern
Improving a form, intake, or handoff
Connecting one known source to one destination with a supported standard connector
A small improvement to an existing application
Includes
Brief discovery and a written scope with acceptance criteria
Implementation or configuration of the agreed change
Essential error and access checks
One walkthrough and concise documentation
A planned allowance for fixing defects against the agreed scope
Not included (scoped separately)
New custom integrations
Multiple user organizations
Data migration or cleanup
Native mobile apps
Custom billing
Formal compliance programs
Substantial security remediation
Ongoing usage charges (model, API, hosting)
Workflow Build
Automate a defined business workflow.
One defined workflow with bounded inputs, one supported integration, and an output or action with the right human review built in. Error handling, operating instructions, and a real handoff included.
Suitable for
One defined business workflow with clear inputs and outputs
One supported integration
An output or action that needs appropriate review
Teams that want operating instructions and a clean handoff, not a black box
Includes
Workflow definition with bounded data inputs
One supported integration
Output or action with appropriate review
Error handling and operating instructions
Handoff to your team
Not included (scoped separately)
New or unfamiliar systems without a scoped onboarding assessment
Large datasets or data migration
Additional roles and permission models
External approval dependencies outside the agreed scope
First Web Release
Ship a bounded first release.
A modest, responsive web application with up to three principal screens, one primary user workflow, one role or an existing managed sign-in pattern, and at most one supported integration. Built on established components, deployed, tested, and handed off.
Suitable for
A defined, useful first release rather than an open-ended product idea
Up to three principal screens and one primary user workflow
One role, or an existing managed authentication pattern
At most one supported standard integration
Includes
Discovery and design for the bounded release
Implementation on established components
Deployment preparation and appropriate testing
Accessibility and quality checks
Handoff and planned defect support
Not included (scoped separately)
Complex SaaS applications and multiple tenants
Native mobile apps
Custom payments
Highly regulated workflows
Anything beyond the defined release scope (priced as its own proposal)
Investment
Focused improvements from $2,500. Larger workflows and product builds are scoped around what you need to achieve.
Quickstart
Focused improvements from $2,500
One validated small improvement with clear inputs and acceptance.
Workflow Build
Defined workflow or integration from $5,000
One defined workflow, bounded data inputs, one supported integration.
First Web Release
A bounded first release from $12,500
Up to three principal screens, one primary workflow, one role, one integration.
Starting prices apply to the scopes above. Work that does not fit is quoted on its actual scope, reduced with you to fit, or preceded by a short discovery step. Specialized enterprise programs are priced on the actual work. Model, API, and hosting usage that your solution consumes is identified separately.
Monthly service plans for a defined, supported solution. Each plan reserves a set amount of human service time, states its response target, and keeps third-party costs separate. These are services, not software subscriptions, and they are separate from LYFYE Readers, LYFYE Facts, and LYFYE Marketing Studio subscriptions.
Plan
Fee per month
Included human service time
Typical included work
Initial response target
Care
$350
Up to 1 hour total
One scheduled health review, small maintenance or configuration fixes, and a concise status note.
Within 2 business days
Improve
$1,250
Up to 4 hours total
Care activities plus a prioritized small improvement, troubleshooting, or an adoption session.
Within 1 business day
Delivery Partner
$2,950
Up to 10 hours total
Prioritized development and automation backlog, releases, troubleshooting, and a monthly planning session.
Within 1 business day, with priority scheduling among contracted work
What the plans include, and what they do not
Business hours are Monday through Friday, 9 a.m. to 5 p.m. Eastern, excluding published US business holidays.
Response means acknowledgment and an assessment of the next action, not a guaranteed fix. Fixes are scoped and scheduled by severity and dependencies.
No 24/7 incident response, breach response, or guaranteed restoration is included in these plans.
All meetings, diagnostics, review, deployment work, and reporting count within the included time. Work is sequenced, not staffed by a dedicated full-time employee.
Unused hours expire monthly because the plan reserves capacity. There is no automatic overage billing: additional work is scoped separately, or agreed at $275 per hour before it begins.
Customer licenses, hosting, model and API usage, and other third-party costs are identified separately and are not included in the monthly fee.
Plans are month-to-month, paid at the beginning of the service month, and cancellation takes effect at the next renewal when requested before that renewal.
Plans cover a defined, supported solution. New or unfamiliar systems receive a separately scoped onboarding assessment first, and a plan starts only after the solution is accepted and the support scope agreed.
Capacity is reserved per client. When reserved capacity is full, sales of additional plans pause rather than stretching response targets.
When the work is bigger than a single offer, it runs in phases with a decision point between each one. Durations are set in the proposal for your program; the ranges below describe the shape, not a promise for every project.
Discovery
Days to 2 weeks
Deliverables
Written objective, scope boundaries, and acceptance criteria
Current-state review of systems, data, and access
Risks and unknowns turned into verification work
Design and planning
1 to 3 weeks
Deliverables
Solution design and integration plan
Statement of work with fixed scope, price, and milestones
Change control and decision points agreed up front
Build
Scoped per program
Deliverables
Working software in reviewable increments
Tests, error handling, and operational instrumentation
Regular demos against the acceptance criteria
Validation and handoff
1 to 2 weeks
Deliverables
Acceptance against the written criteria
Documentation, runbooks, and knowledge transfer
Planned defect support, then an optional care plan
Every engagement starts with a written scope
Before work begins, the agreement defines:
Deliverables with acceptance criteria
Boundaries: what is included and what is scoped separately
Timeline with decision points
Who does the work and who decides at consequential boundaries
Price, payment terms, and how additional work is agreed
Ready to start?
Tell us what you want to build. We respond with the engagement mode that fits, the scope, the deliverables, and the price. If the answer is not to build yet, we tell you that too.