Skip to content

Our Process

Contact, a real discussion, then the work. The same three steps, with the detail filled in.

A project starts when you describe the problem, not when a package is picked off a list. The scope, the price, and the schedule are set against your systems. After that, the records of the job stay somewhere you can find them.

  • New work goes to sales. Existing clients use service.
  • Hourly, fixed price, or a monthly retainer, said before you commit
  • You own the code and the accounts when the project ends
  • Hours are 8:00 to 4:00, Monday to Friday, Central. Call (629) 234-2569

Step 1

Contact

Call (629) 234-2569 or write to sales@triwaveconsulting.com. Say what is slowing the business down: the step someone repeats, the page that should start an enquiry, or the two systems that do not share a record. That is enough to start. A polished brief is not required.

New work uses sales@triwaveconsulting.com. If you are already a client, service@triwaveconsulting.com is the address for the job in progress. Hours are 8:00 to 4:00, Monday to Friday, Central. A message that arrives later is picked up the next working day. If something is urgent, say so.

The first reply is about your situation. It is not a pitch for every service on the site. If the work is a poor fit, that gets said here, before a proposal exists.

Step 2

Discuss

The second step is a working conversation. We look at the systems you already run, what has to stay, and what the finished job has to do. Two projects that sound the same can sit weeks apart once the data and the old software are visible, so the schedule is scoped for this job rather than taken from an average.

Billing is chosen the same way. Hourly fits work whose scope will genuinely move. A fixed price fits work that can be defined up front. A monthly retainer fits maintenance and support that continue after launch. Which one fits, and why, is said before you commit. The price is a quote for your project. There is no published rate card.

What you agree is written down as a proposal: the work, the price, and what is out of scope. You review it before anything is built. Signing it is the point where the job starts, not the first phone call.

Step 3

Implement

The agreed plan is what gets built. Progress is checked against that plan, and the plan is adjusted when the systems turn out to be different from the description. You hear about that change before the work drifts.

A website engagement includes the unglamorous part: domain and DNS, backups, software updates, security monitoring, and spam. Custom software includes updates, bug fixes, performance, and help when a screen is not behaving. Support after launch is part of the job when the proposal says it is, usually as the retainer.

At the end, the code, the domain, the hosting, and the third-party accounts are in your name. You can keep them, move them, or hand them to someone else. Staying is a decision about the work, not a lock on the accounts.

Where the Records of the Job Live

The client portal at portal.triwaveconsulting.com is the place those records are being gathered: proposals, invoices that have been sent, support requests, and files shared for a project. Sign-in is not open yet. Until it is, the same records are sent directly, by email. An empty portal page is not a zero balance and it is not a closed ticket.

  • Proposals

    A proposal is the scoped job: what will be done, what it costs, and what is left out. Drafts stay in the office. You see the one that is ready to review, and the job starts when you accept it.

  • Invoices

    Invoices are emailed when they are sent. Pay by card through Stripe, or by check if that suits the accounts. A draft is not a bill. The portal will list the invoices that have been sent, once sign-in opens. Paying on the portal itself is not available yet.

  • Support

    Existing clients write to service@triwaveconsulting.com. That is the queue for something that is not behaving, a change to a live site, or a question about an invoice. The portal's support list is the same queue, once an account can sign in. Until then, the email is the request.

  • Files

    Project files that are meant for you — a handover note, an export, a login list — are sent directly today. The portal's documents area is where those files will sit with the account, rather than in a thread that is hard to find later.

What you keep

The code, the domain, the hosting, and the third-party accounts are yours at the end of the project. Billing details on the account, when the portal can show them, are read from the office record. A change to the legal name, the address, or the invoice email goes through us, so the accounting record stays the one the invoices are sent from.

A short note each month on software, automation, and online presence. No recycled posts, and no pitch dressed up as advice.

Questions?

Tell us what is slowing the business down. We will say which of the work actually helps, and which of it can wait.