Process
How it works
I use the 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. I will walk you through the process and 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
I write what is in, what is out, and a number you can live with. We settle ownership and access before any deposit so the build does not stall mid-flight. Hosting and upkeep are assumed unless the package says otherwise.
- Category + tier (or a custom quote when packages do not fit)
- Inclusions, out-of-scope items, and revision expectations
- Access needs: domain, app stores, APIs, accounts
- Deposit only after you approve the written scope
Build
In-house, with me on the work. 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
We go live. Let me take care of the maintenance and upkeep. I host by default on websites and on other projects unless the package says otherwise. If you want the source code, ask and I will hand it over. Consulting stays available when you need ongoing eng work beyond hosting care.
- Hosting and upkeep assumed unless the package says otherwise
- Source code available on request (not a default dump)
- Launch checklist for sites, apps, and workflows
- Upkeep (hosting) vs consulting retainer kept separate
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 I sell.
Website
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 on hosting I run, with upkeep included in the hosting plan.
Custom software
Custom Software
Portals, dashboards, and internal tools. Talk maps the real workflow. Scope lists roles, data, and integrations. Build ships checkpoint demos against your process. Launch assumes I host and maintain unless the package says otherwise. Source is available if you ask.
Mobile
Mobile App
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 is code-only: you own Apple/Google store accounts. Runtime care when hosting is in the package.
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 with me unless you want to run it yourself.
Ongoing support
Consulting
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
Services & 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 business website often takes around 3–6 weeks, depending on the scope and how quickly content and feedback come together. Custom software, mobile apps, and larger automation projects get a written timeline after we've worked through the scope. Smaller one-time jobs and audits can move faster.
- Do you work with clients outside Wisconsin?
- Yes. Most of my work is remote, and I work with clients nationwide from Wisconsin's Central Time Zone. You get a direct line to the person building your project, regardless of where you're located.
- What do you need from me to get started?
- A rough description of what you're trying to build, any existing links or materials, and a little context about where you're at now. If you already have a domain, website, software, or existing tools, send those along too. Messy notes are completely fine. We can sort through the details together. Scope a Project.
- Do I own my website and code?
- Yes. You own the work created for your project. CreativeBuilds hosts and maintains websites by default unless your package or agreement says otherwise. If you want your source code or need to move your project elsewhere, you can request it. Any third-party assets, licenses, or services used in your project are documented as part of delivery. Read the Terms.
- Who will I actually work with?
- You'll work directly with Ryan Baldwin, the developer behind CreativeBuilds. For larger projects, I may bring in additional specialists when a project benefits from extra expertise. The project, communication, and overall direction stay with the same shop. Meet the Team.