Process
How it works
Same four steps for websites, custom software, mobile apps, automations, and ongoing support. No mystery. You always know what happens next.
Talk
You send the message or book a call. We get clear on the job: what is broken, what done looks like, and which lane fits (website, custom software, mobile, automations, or ongoing support). Messy notes are fine.
- What hurts today, and what done looks like in plain English
- Tools, sites, or apps you already use
- Domain status when a public site is involved
- Timeline pressure and who decides on your side
Scope
Written what, what not, and a number you can live with. We settle ownership and access before any deposit so the build does not stall mid-flight.
- Category + tier (or a custom quote when packages do not fit)
- Inclusions, out-of-scope items, and revision expectations
- Access needs: domain, hosting, app stores, APIs, accounts
- Deposit only after you approve the written scope
Build
In-house. You get updates you can follow and working checkpoints, not a ticket void. What you see depends on the job: site previews, app builds, automation dry-runs, or retainer work logs.
- Same shop from first commit through launch
- Checkpoints matched to the deliverable type
- Questions answered without a support maze
- Scope changes get a clear yes/no and price impact
Launch
You own what we ship. We go live, hand off source and docs, and leave a clear path for what comes next: hosting upkeep, store submission, automation monitoring, or a Compass retainer for ongoing eng work.
- Source handoff on custom builds
- Launch checklist for sites, apps, and workflows
- Upkeep (hosting) vs Compass (eng retainer) kept separate
- Optional audits or SEO add-ons when you already have a property
Across every service line
The spine stays the same. The checkpoints change with the job. Here is what Talk through Launch looks like for each line we sell.
Presence
Website
Public sites and landing pages. Talk covers brand, pages, and goals. Scope locks hosting tier and domain keep/transfer/buy. Build uses staged previews. Launch goes live with optional monthly upkeep.
Custom software
Forge
Portals, dashboards, and internal tools. Talk maps the real workflow. Scope lists roles, data, and integrations. Build ships checkpoint demos against your process. Launch includes source handoff and hosting guidance.
Mobile
Pocket
iOS, Android, or both. Talk decides who uses the app and offline needs. Scope caps screens and features honestly. Build uses TestFlight / internal tracks. Launch covers store submission support when that is in scope.
Workflows
Automations
Connect tools, kill copy-paste, schedule reports. Talk lists the repetitive steps. Scope names systems and failure alerts. Build dry-runs against real accounts. Launch leaves monitoring and docs your team can follow.
Ongoing support
Compass
Engineering help after something already exists. Talk sorts fixes vs features vs coaching. Scope sets hours, tickets, and response window. Build here means the retainer cadence. Launch is continuity, not a one-time go-live.
One-time
Audits & add-ons
SEO, UX, and punch-list work when you already have a site or app. Talk defines the question. Scope picks the audit depth. Delivery is a written report and next steps, not a full rebuild unless you ask for one.
Common questions
- How long does a typical project take?
- A focused marketing site often lands in 3 to 6 weeks, depending on how ready your content is. Forge tools, Pocket apps, and bigger automations get a written timeline after we talk through scope. Small one-time jobs and audits move faster.
- Do you work with clients outside Wisconsin?
- Yes. Most of our work is remote. We are based in Wisconsin (Central Time) and work with clients nationwide.
- What do you need from me to start?
- A rough description of the problem, any existing links or materials, whether you already own a domain, and time for a short call. Messy notes are fine.
- Do I own the code?
- Yes. Custom builds include source handoff. Licensing for any third-party assets is documented when we deliver.
- Who is on the team?
- You get a direct line to Ryan. Bigger jobs can pull in helpers for craft depth. Ownership of the build and hosting stays with the same shop. Meet everyone on the Team page.