All services
Software / Web + mobile

Your workflow.
Built into software.

We build software around the people using it: a customer opening an account, a crew posting an update or a team managing daily work. Web and mobile development include UI/UX design, from user flows and prototypes to responsive screens and the states between them. We agree the platforms, core workflow and release scope before the build.

From $4,999Web software $4,999 · mobile $7,999
SiteLedger desktop demonstration dashboard with fictional records
SiteLedger mobile demonstration with fictional records
Defined scopeDesign reviewTested key pathsDocumented handoff

One product. Across the screens that matter.

SiteLedger connects field activity, project records and timelines in a shared workspace. Its desktop and mobile previews show how a shared workflow adapts to the people using it, at a desk or on a jobsite.

SiteLedgerSiteLedger / construction operations
SiteLedger desktop dashboard with fictional project records, activity and a connected timeline
SiteLedger desktop dashboard · fictional demo data

The same system.
A different screen.

Mobile software starts with the job away from a desk: check a project, capture an update or review the working day. The layouts and touch interactions are designed as part of the product.

The field.
The working day.

Project updates in SiteLedger.
Daily work in Mission Control.

SiteLedger mobile demo showing field projects and activity
Mission Control mobile demo showing daily tasks and a command dashboard

Map the task before the build.

Choose an example to see the people, information and acceptance checks we define before turning a workflow into software.

Example / Customer portal

A request your customer can follow.

Give customers one place to see their own records and ask for help without repeating their account details.

  1. 01Sign in
  2. 02View own records
  3. 03Send a request
People & permissions
Customer · account manager · administrator
Information to model
Account, membership, request, status and attachments.

What we agree to test.

Customers can only access their own records.

Missing information produces a clear next step.

A submitted request has a stored record and honest confirmation.

When something goes wrong

An expired session returns the customer to sign-in without revealing another account’s information.

What you review before development

Screen map, account-access rules, request fields and a tested confirmation flow.

Map your product flow

Web and mobile apps for your business.

Web software & SaaS products

Customer portals, dashboards, SaaS MVPs and internal tools with the agreed accounts, permissions, data and business workflows.

iOS, Android & mobile experiences

Customer apps, booking, field tools and connected mobile workflows, with device features, connectivity and distribution defined in scope.

UI/UX design included

User journeys, wireframes, responsive interfaces and prototypes for the agreed product, including loading, empty, error and permission states.

Connected data & integrations

Shared accounts, records and business rules across the agreed platforms, with provider access, migration and usage costs reviewed before implementation.

Define the product, platforms and first release.

Web software and the core workflow

Define the users, account model and one complete workflow for a portal, dashboard, SaaS MVP or internal tool. Agree the screens, records, permissions and any billing integration before the build.

Mobile apps and device requirements

Choose iOS, Android, an installable web app or responsive mobile web around the task. Specify booking, field updates, photos, notifications, device access and connectivity where required.

Product design & interaction

The development scope includes user flows, wireframes, responsive interface design and prototypes for the agreed product. Review navigation, touch targets, accessibility and loading, empty, error and permission states as part of the build.

Shared data and existing tools

Agree the data model, account isolation, user roles and connections between web and mobile. Review provider APIs, access, migration and recurring usage costs before including an integration.

Testing, release and handoff

Agree the browser and device checks, distribution route, access and documentation. Developer accounts, signing, store review and third-party fees are release dependencies; ongoing support and later features are scoped separately.

One-time builds

A clear starting budget.

Web software, a mobile app or one connected product. Agree the scope and first release before the build.

Starting prices · final scope quoted

Web software

A focused portal, dashboard or first product workflow.

From$4,999/ project · USD
  • One core workflow, up to 6 primary screens
  • User flows, custom UI/UX and responsive layouts
  • Account access and agreed user permissions
  • One core data model and one agreed integration
  • Validation, key error states and handoff

Mobile app

A focused cross-platform app connected to a shared backend.

From$7,999/ project · USD
  • One core workflow, up to 8 primary screens
  • User flows, custom UI/UX and touch-first layouts
  • One shared cross-platform app codebase
  • Account access and core backend connection
  • Device testing and agreed release preparation

Web + mobile bundle

One connected product, built for the desk and the phone.

From$10,999/ project · USD

Save $1,999 versus $12,998 for the two starting packages separately.

  • The web-software and mobile-app starting scopes in one project
  • One shared core workflow, account model and backend
  • UI/UX designed together across web and mobile
  • Up to 6 web screens and 8 mobile screens
  • Coordinated testing, release preparation and handoff

Aftercare is optional. No ongoing plan required.

Discuss the bundle

For web and mobile commissioned together around the same workflow and backend. Independent products, additional workflows and extra integrations are quoted separately. Care is never added automatically.

Scope first. Fixed quote next.

UI/UX is included, not a separate service fee. These are starting budgets for a focused first release, not a quote for every app. We agree the screens, workflow, permissions and acceptance checks before a fixed proposal.

Subscriptions, hosting, paid APIs and store accounts are separate. Offline sync, complex migrations, additional integrations and store submission are included only when agreed. Optional maintenance is listed below; new features and larger releases need their own scope.

Ongoing support

Care after launch.

Optional maintenance, separate from the build. Choose monthly billing or pay for a year upfront. Annual prepayment saves two months.

Optional care · monthly or annual billing

Web software care

Ongoing care for a portal, dashboard or focused web product.

Up to 3 maintenance hours per month, total.

Monthly
$499/month
Annual prepaid
$4,990/year

Save $998 vs. 12 monthly payments.

  • Application health, dependency and security checks
  • Bug fixes and small changes to existing workflows
  • Release checks and a monthly maintenance summary
Discuss software care

Mobile app care

App, device and backend upkeep for a cross-platform product.

Up to 5 maintenance hours per month, total.

Monthly
$799/month
Annual prepaid
$7,990/year

Save $1,598 vs. 12 monthly payments.

  • OS compatibility, dependency and security checks
  • Bug fixes across the agreed app and backend
  • Release preparation and a monthly maintenance summary
Discuss mobile care

All prices in USD. Annual billing replaces monthly billing; the full annual amount is paid upfront. The same monthly hour limit applies to either option, including checks, fixes and reporting; unused hours do not roll over. Extra work needs an approved quote. New features, redesigns, major upgrades, migrations, hosting, paid APIs and store accounts are separate. Coverage and response windows are agreed before the plan starts; these plans do not include 24/7 incident cover or a guaranteed resolution time.

From user flow to web and mobile release.

Phase 01

Define the product

Map the users, workflow, data and permissions, then choose the web and mobile platforms the first release needs.

The questions we resolve

  • Who can read and change each record?
  • What must the first release complete?
  • Which connections and provider costs are in scope?

Before we start.

How is software and mobile development priced?

We quote the agreed first release around its workflows, screens, platforms, data, permissions and integrations. UI/UX design for that scope is included. Device features, offline sync, migration and distribution affect the quote; provider fees and ongoing support are identified separately. Website package prices apply to website builds.

Is UI/UX design included?

Yes. Software and mobile development include the user flows, wireframes, responsive screens and prototypes needed for the agreed product, followed by implementation. We define the screen list, review points and interface states together before work begins.

Do I need a mobile app or a mobile website?

That depends on repeat use, distribution and device features. We compare responsive mobile web, an installable web app and an iOS or Android app, then agree the platforms and build approach. A project can cover web, mobile or both.

Can the web and mobile apps share accounts and data?

Yes, when included in the scope. We define shared accounts, records and business rules alongside user roles and account-level data isolation. Permissions and data boundaries are part of implementation and testing.

Will the app work without an internet connection?

Offline access needs an explicit scope: which records stay on the device, what can be edited, how changes sync and how conflicts are resolved. We agree those behaviors before including offline support.

Does the project include an App Store or Google Play launch?

When distribution is included in the agreed scope. It requires the appropriate developer accounts, signing, device checks and store review, with any fees identified separately. Store approval remains subject to the platform’s review.

Can it connect to tools we already use?

Often, subject to the provider’s API, access and plan. We confirm those dependencies, data handling and usage costs before including an integration in the build.

What happens after release?

You receive the agreed access, documentation and handoff. Optional web-software and mobile-app maintenance plans are listed below the build packages, with monthly or annual-prepaid billing. We agree coverage and hour limits before a plan starts. Major new features and future releases are quoted separately.

Build the software your work needs.

Tell us about your project