Clarity before commitment / 01

Know the work.
Know the terms.

What you pay. What gets delivered. Who does what. How we confirm success. No vague “AI transformation” promises or surprise engineering invoices.

OUR OPERATING PRINCIPLE

Clear work.
Clear ownership.

  • Defined scope, capacity or deliverables
  • Written acceptance criteria before build
  • Transparent deposits and milestones
  • Client retains control of client-owned systems
  • Documented handoff and exit
How agreements work ↗
02 / Engagement options

Start where it makes sense.

These are illustrative starting packages. Your actual quote is based on complexity, access, and measurable requirements.

01 · Before building

Automation diagnostic

$2,500

Typically 5–10 business days. A paid investigation of the workflow and opportunity.

  • Workflow and systems map
  • Prioritized opportunities
  • Feasibility + integration plan
  • Scope and implementation estimate
Start with discovery ↗
02 · Defined first win

Automation pilot

From $8k

Typically $8k–$15k. Deliver one agreed workflow with a testable definition of done.

  • One agreed automation
  • Integrations and testing
  • Documentation and deployment
  • 50% to start; 50% on acceptance
Scope a pilot ↗
04 · After launch

Managed systems

$1,500+ / month

Monitoring and scoped maintenance for the software that runs your work.

  • Monitoring and exception review
  • Defined maintenance allowance
  • Monthly service report
  • New features scoped separately
Discuss ongoing support ↗

All prices in USD. Cloud, API, model usage, third-party licenses, applicable taxes, and agreed travel are additional unless listed in your signed SOW. The diagnostic and FDE amounts are recommended launch prices, not guaranteed public quotes.

03 / Engagement lifecycle

From first contact to handoff.

Each stage has an owner, a deliverable, and an explicit next action.

01RequestTell us the broken workflow
02DiscoveryFit, budget, access, success metric
03ProposalScope, fees, exclusions, acceptance
04AgreementMSA + SOW, authorized signature
05PaymentSecure checkout, confirmed by Stripe
06Build & reviewWeekly demo, tracked approvals
07Accept & operateTests, final invoice, handoff/renewal

What you'll see in the client workspace

  • Exact quoted fee, billing schedule and initial term
  • In-scope and out-of-scope work
  • Measurable acceptance criteria, not vague “success”
  • Agreement text and audit reference
  • Secure payment step and current payment status
  • Milestones with evidence and feedback requests
  • Onboarding owner, access plan and handoff status
View example experience ↗

What we'll need from you

A project sponsor who can make decisions; staff who understand the workflow; appropriately provisioned system access; representative test cases; and timely feedback on demos. Delays in these dependencies can change the timeline.

What we don't promise

No guaranteed revenue increase, automation accuracy of 100%, unlimited capacity, immediate deployment without access, or unrestricted model/data usage. Baseline and outcome metrics are agreed during discovery.

04 / Commercial expectations

Nothing important in the fine print.

ScopeDefined in the SOW; changes must be approved before work begins.
BillingDiagnostic upfront; pilots typically 50/50; embedded and managed packages monthly in advance.
FDE capacityUp to 60 engineering hours/month at the illustrative $9,500 tier; unused hours do not roll over.
Extra workGenerally $185/hour only with written pre-approval.
AcceptanceAgainst specified test cases and deliverables. Reviewers can approve or request specific changes.
OwnershipClient-specific paid deliverables and Photoxpedia background IP are handled separately in the signed MSA.
SecurityLeast-privilege access; never paste secrets in intake forms; special data needs additional agreements and controls.
SupportSupport windows, response targets, and aftercare only as expressly stated in the SOW.

What gets signed?

Our commercial document flow is designed around an attorney-reviewed Master Services Agreement plus a project-specific Statement of Work. The sample in this project is a demonstration template, not an executed legal contract.

When do we start?

After agreement approval, verified payment, and access onboarding. A card redirect alone does not count as confirmed payment.

When is the job done?

At acceptance against agreed criteria, plus final payment when applicable, followed by a written handoff or new support agreement.

Start a conversation ↗
05 / Questions

Answers before the contract.

Does “embedded” mean full-time or on-site?

Not by default. The advertised FDE tier reserves up to 60 engineering hours per month. Working model (remote, hybrid or on-site), availability, meeting cadence and travel are explicitly agreed in the SOW.

Do you own everything we build?

Your ownership rights are governed by the signed MSA. We propose assignment of fully paid, specifically commissioned deliverables while retaining pre-existing software, reusable tooling and frameworks, with appropriate licenses.

What if the automation doesn't pass our test?

Request changes in the client workspace and identify the failed agreed criteria. We'll triage defects within scope. New capabilities or changed requirements go through a written change order.

Is the diagnostic refundable?

No refund promise is implied. The diagnostic is paid professional work with a defined set of deliverables. Any cancellation/refund conditions are stated in the signed agreement.

Can you handle sensitive data?

Only after evaluating requirements and signing any necessary data-processing, confidentiality or HIPAA-related documents. Access is provisioned separately; passwords and protected records should never be submitted in a general contact form.