Show us the work.
Walk through the problem, your tools, and what you want to improve. The initial call is free.
Your involvement
Bring an example. No finished brief or SOP needed.
The 2690 Build
A clear plan.
Working progress you can see.
From the first conversation to launch, know what you’ll receive and when we need your input.
Let’s talk about your projectOne workflow.
A useful first build.
We connect your tools and build the missing internal app around how your team works.
What you get
- A workflow map and agreed build plan
- Working software, reviewed in milestones
- Training, documentation, and handover
- An agreed stabilization and support plan
From $10,000
Small sprints from 3 weeks. Larger builds are scoped in phases.
Scope, price, schedule, payment milestones, and expected running costs are agreed before work begins.
Matt is your point of contact. Throughout.
For questions, updates, or decisions, come to Matt. He coordinates the work and brings Mike into technical conversations when needed.
First, two conversations.
Review the proposed build.
For qualified projects, we show a focused prototype and walk through scope, pricing, and timing.
Your involvement
Bring the workflow owner and whoever approves the investment.
Here’s what the build looks like.
We agree on review dates at kickoff. Between reviews, we build and test. Blue panels show when we need your attention.
01 · Define
Agree on the plan.
We map the steps, owners, exceptions, and approvals.
What you get
Workflow map, scope, milestones, and completion checks.
Brief submitted↓Creative review↓Approved for launch
Your involvement
Show us how it works. Approve the plan.
Your workflow owner joins the review; your approver confirms scope and budget.
02 · Build
Try working versions.
We build and test in a separate environment, with walkthroughs at agreed milestones.
What you get
Working demos and clear requests for feedback.
Creative review Test environment
Spring campaign
Concept 02
Concept 02
Reviewer: Brand lead
Awaiting feedback
Awaiting feedback
Your involvement
Try the demo. Share consolidated feedback.
Bring the people who will use it. We tell you what to test and when feedback is needed.
03 · Launch
Approve live use.
We complete technical checks, plan recovery, and verify the release after launch.
What you get
Acceptance checklist, release plan, and verified live workflow.
Launch checks
✓ Approved asset matches
✓ Destination checked
✓ Tracking checked
Next: your launch approval
Your involvement
Check the workflow. Approve launch.
Your named approver confirms readiness after the agreed checks pass.
04 · Handover
Get your team ready.
We train your team and confirm ownership, access, and support.
What you get
Live training, recordings, operating guide, code, and account documentation.
Running your creative workflow
Recorded walkthrough
Operating guide · Account inventory · Support contacts
Your involvement
Attend training. Confirm your team can use it.
Include the users and the person who will administer the system.
Process still taking shape? If more interviews or workflow mapping are needed after the first two calls, Matt’s time is included in Phase 1, the project price, and the schedule.
Updates you can act on.
Matt keeps the next step clear. We agree on the update channel and review schedule at kickoff.
Example project update
Creative approvals · Milestone 1
- Ready to review
- Submit a brief and route it to an approver.
- Your decision
- Confirm who can approve and request changes.
- Next milestone
- Connect approved assets to launch readiness.
Written updates + Loom
Short progress notes and walkthroughs you can review when convenient.
Calls when needed
Kickoff, milestone reviews, decisions, and training. We agree on the dates together.
One place for decisions
We record approvals and changes in the shared project view. Email is the default; a shared Slack channel can be agreed.
DIALED across every phase.
Our engineering and delivery process covers specification review, code review, testing, traceable releases, and recovery planning. Your team checks the business workflow; we own technical implementation and testing.
Working together.
Pricing and payments
Your proposal states the scope, payment milestones, schedule, and expected hosting, software, and usage costs. Additional workflow definition is part of the build. We explain price and timing changes before asking you to approve new scope.
Your time and feedback
We agree on the people, review dates, and expected participation at kickoff. Choose one person to collect team feedback. If access or a decision is delayed, Matt explains the schedule impact.
Access and ownership
We agree on ownership before the build and confirm it at handover: code, hosting, accounts, configuration, billing, and administration. Credentials are shared securely, not in ordinary email or Slack messages.
Support after launch
Your proposal defines stabilization, support coverage, the contact channel, and initial response expectations. Response time and resolution time are separate. Contact Matt for help.
Ongoing improvements
Stewardship adds ongoing support and agreed development capacity. We prioritize improvements together and confirm what needs a separate estimate.
Bring the workflow
you want to improve.
Start with Matt. We’ll help you work out a useful first step.
Let’s talk about your project