LJ App Solutions packages. Fixed-price systems, Connector, marketing sites, and consulting. Book a scope call or contact contact@ljappsolutions.com.

Packages

Fixed price systems. Agent connectors. Custom quotes.

System packages are fixed scope, counted in workflows. Connector is fixed scope, counted in MCP tools over one data source (an API, spreadsheet, document set, and similar) for teams that need agents on their data without a new UI. Marketing sites and consulting hours are time & materials after a short discovery call. Timelines start when the written scope is signed and access is in hand.

Pilot

3–4 weeks · up to 3 workflows

Best for

A focused first release: quote-to-invoice, permit issuance, a payment session, or a small assessment loop with the related admin paths.

Included

  • Written scope
  • Up to three workflows in production
  • Sign-in · one primary role + admin
  • Deploy on cloud accounts you own
  • Basic admin · transactional email
  • 1 week post-launch fixes · handover notes

Not included

  • Payments or subscriptions
  • More than three workflows
  • Third-party API fees
  • Ongoing care
Book a scope call

Product

Most chosen

5–7 weeks · up to 6 workflows

Best for

A product people log into daily: several connected outcomes, roles, admin, payments, and one or two integrations.

Included

  • Everything in Pilot
  • Up to six workflows
  • Two roles beyond admin
  • Stripe (one pricing model)
  • Up to two integrations
  • Polished primary screens · weekly demos
  • 2 weeks post-launch fixes · short runbook

Not included

  • Native mobile apps
  • Marketplace or multi-vendor
  • Heavy legacy migration
  • Compliance programs
Book a scope call

Platform

8+ weeks · up to 10 workflows

Best for

A broader ops or SaaS foundation: many connected outcomes, entitlements, or collapsing a tool patchwork into one owned system.

Included

  • Everything in Product
  • Up to ten workflows
  • Org-fit role model
  • Billing + entitlements
  • Up to four integrations
  • Staging + production · observability basics
  • Architecture notes · 4 weeks post-launch support · v2 roadmap sketch

Not included

  • Large migrations
  • Open-ended retainers inside the package
Book a scope call

Connector

MCP · agents

2–3 weeks · up to 8 tools

Best for

Teams that already use Claude, Cursor, or ChatGPT and need agents to use one data source safely (a CRM or API, Google Sheets, PDFs, tickets, orders) without commissioning a new website or portal.

Included

  • Written tool list and permission model
  • One MCP server over one source
  • Up to eight named tools with typed schemas
  • Auth · audit log · rate limits
  • Deploy on infrastructure you own
  • Client setup for Claude and Cursor
  • Runbook · 2 weeks post-launch fixes

Not included

  • New websites, portals, or dashboards
  • More than one source (available as an add-on)
  • Customer-facing multi-tenant MCP
  • Unrestricted write tools without confirmation rules
  • Ongoing protocol care (available separately)
Book a scope call

Marketing site

Time & materials

Scoped per project · time & materials

Best for

Brand and brochure sites, content-led launches, and redesigns, quoted time & materials after a short discovery call.

Included

  • Discovery call and written estimate
  • Time & materials against an agreed rate
  • Design and build scoped in writing before each phase
  • Deploy on hosting you own (or we advise)
  • Handover notes and CMS training when needed

Not included

  • Open-ended retainers without a written estimate
  • Unlimited redesign rounds inside one estimate
  • Ongoing care (available separately)
Request a quote

Consulting

Time & materials

Scoped per engagement · time & materials

Best for

Senior engineering hours for cloud hardening, compliance-oriented technical reviews, AI assessments, and delivery risk, quoted time & materials after a short discovery call.

Included

  • Discovery call and written estimate
  • Time & materials against an agreed rate
  • AWS environment hardening
  • SOC 2 technical readiness and technical audit support
  • AI and coding-agent assessments
  • Architecture and delivery reviews for existing products
  • Cloud cost and observability passes on AWS you already run
  • Written findings and next-step recommendations

Not included

  • Open-ended retainers without a written estimate
  • Fixed-scope product builds (see Pilot, Product, Platform)
  • Fixed-scope MCP builds (see Connector)
  • Formal certification or auditor-of-record work
Request a quote

Scope units

How we count work before we build

System packages are counted in workflows. Connector is counted in MCP tools over one data source (API, spreadsheet, documents, and similar). Both use a plain-language sentence so scope stays fixed and change orders stay honest.

What counts as a workflow

A workflow is one role getting one result end to end: the screens, steps, and usual edge cases for that path. If you cannot finish the sentence “When ___ does ___, the system ___,” it is not scoped yet. Shared pieces like sign-in and admin count once for the whole product.

When [role] does [action], the system [result].

Examples of one workflow

  • Facility manager records asset condition → capital plan updates with recommended work.
  • Staff sends an estimate → client accepts and it becomes an invoice.
  • Operator issues a parking permit → patron gets confirmation and access rules.
  • Security officer searches a vehicle plate → sightings across every site and camera appear in one timeline.
  • League scheduler builds a season → teams and venues land without conflicts.
  • Patron pays for a parking session → operator sees the receipt and occupancy.
  • Member finishes an assessment → scored report and plan appear on their dashboard.
  • Publisher prepares a title → print-ready listing assets are ready to launch.

Not a separate workflow

  • Sign-in, roles, admin shell, and basic notifications: shared foundation, not a separate workflow.
  • “Build us a CRM,” “all reporting,” or “the whole ops stack”: those are several workflows (or a custom quote).
  • Stuffing many unrelated features onto one screen does not make them one workflow.

What counts as a tool

A tool is one named action an agent can take against a source: fixed inputs, a clear return shape, and an explicit permission. If you cannot finish the sentence “When the agent needs to ___, it calls ___ and gets ___,” it is not scoped yet. Auth, logging, and deploy count once for the whole Connector. A source is one place the data lives (an API, Google Sheet, PDF set, and similar).

When the agent needs to [job], it calls [tool] and gets [result].

Examples of one tool

  • Look up a customer by email → account record and open tickets.
  • List overdue invoices for an account → amounts, due dates, status.
  • Get order by id → line items and fulfillment state.
  • Read a row from an ops Google Sheet → fields the agent needs for a decision.
  • Extract fields from an uploaded PDF → structured values for the next step.
  • List today’s appointments for a calendar → title, time, attendees.

Not a separate tool

  • Auth, audit logging, rate limits, and deployment: shared foundation, not separate tools.
  • “Connect our CRM,” “expose the database,” or “full agent access”: those are several tools (or another source).
  • Unrestricted writes (delete records, move money) without a confirmation rule: out of Connector scope.

Scope calculator

Which system package fits?

Four questions for product work: how many workflows, who logs in, whether money moves, and how many outside systems connect. Need agents on your data instead of a UI? Choose Connector. Marketing sites and consulting skip this and go straight to a custom quote.

How many workflows do you need?
Who logs in?
Does money move through it?
How many outside tools must connect?

Add-ons & terms

Clear extras. Clear payment.

Care runs on cloud accounts you own. Your AWS bill stays yours. Packages stay fixed; change orders are written before work.

Care plans

Care - Light

Keep it healthy on your AWS: updates, monitoring follow-up, backup checks, up to 2 hours of small changes. Business hours.

Care - Active

Everything in Light plus up to 6 hours of feature or fix work per month. Business hours.

Care - Connector

Keep your MCP server current: protocol and client updates, log review, up to 4 hours of new tools or permission changes. Business hours.

Add-ons

Extra workflow

One additional workflow inside the chosen system package.

Extra MCP source

One additional data source inside a Connector package (beyond the one included), for example another API, Google Sheet, or document set.

Extra integration

Another CRM, calendar, payments, or accounting connection.

Data migration

Import from sheets or a legacy database with a validation report.

How payment works

  1. Validation week

    10% non-refundable

    About one week against the written scope, enough to prove direction on the primary workflow. If you stop, the project ends; you keep what that week produced.

  2. Build

    60% before continuing

    No further work until this clears. Covers implementation through a final-review-ready build.

  3. Release

    30% after final review

    Paid after you accept the review build. Nothing goes public until 100% is received.

You own the code, repositories, and cloud accounts. Warranty windows are 1 / 2 / 4 weeks by system package; Connector includes 2 weeks. The clock starts when scope is signed and required access is in hand. One active build at a time. Above Platform, or customer-facing multi-tenant MCP, is a custom fixed quote. Extra MCP sources are an add-on. Marketing sites and consulting are time & materials against a written estimate.

Book a 30-minute scope call

We confirm the package, list your workflows, MCP tools, site goals, or consulting needs in plain sentences, and send a written path: fixed scope for systems and Connector, or a time & materials estimate for marketing sites and consulting. Prefer email? contact@ljappsolutions.com

Package interest
Scheduling
Loading availability for this week