A client portal for your customers
Customers sign in and see their own status, files, and invoices, so the question they used to phone about is on the screen. It runs on your domain, and each customer sees only their own records.
Reno, Nevada
Custom software for Reno businesses that outgrew off-the-shelf tools.
Thomas and Jakob Beach write the software from Reno, NV, and Austin Whan keeps the project moving. It ships in a repository, hosting, and cloud accounts your business owns, with notes your next hire can read.
Who calls us
The businesses that call.
The company runs on one spreadsheet that three people edit at once. Somebody sorts a column, a row lands under the wrong customer, and the invoice goes to the wrong address.
The owner pays for four subscriptions that do not talk to each other. A booking goes into one, the invoice is typed into a second, and the customer's email is pasted into a third.
Customers keep calling to ask where the job stands or what they still owe. Each call is a person reading out a screen that a portal could show the customer.
What you get
Six things that ship with the software.
Internal tools and dashboards
Built around how your team actually works: the fields your dispatcher fills in and the report your bookkeeper pulls on Friday. No screens for features you did not ask for.
Booking, uploads, and payments connected
Online booking, file uploads, and card payments land in the tools you already use, so a booking shows up on your crew's calendar and a payment where the books are kept.
Integrations that end the re-entry
Your CRM, accounting software, and email connected, so a new customer is typed once and appears in each. Where a vendor offers no connection, we say so on the first call.
Hosting, code, and accounts in your name
The source repository, the hosting, the cloud account, and the admin logins are opened in your business's name from the first day. If we part ways, you keep all of it.
Documentation and a handover your next hire can read
Setup notes that say what the system does, where it runs, how to deploy a change, and which vendor holds which account. We train the people who will use it, and the notes live in your repository.
How it works here
From the first call to the handover.
The first call
You describe what the business does and where the work stops. We ask who will use the software, what it connects to, and what moves over from the spreadsheet. Thomas or Jakob takes the call and writes the code.
The written quote
You get one fixed price and a schedule in writing before anything is built. If the scope grows, we quote the change first. We use AI tools to assist with development and testing, and a person reviews the work before delivery. Our quoting process is on the pricing page.
The build
We build on a staging address, so you use the real software on your own phone as it takes shape, and nothing goes live until you approve it. A short working trial can come first, so you see it before committing to the full build.
The handover
At launch, the repository, the hosting, the cloud account, and the admin logins are in your accounts, with the documentation next to the code. From there you stop, or move to Managed and we hold the system month to month.
A real example
One live, one on staging.
Mason's Yard Care
A Reno yard care company whose website needed to take bookings. We built online booking, a quick estimate tool, and Spanish-language pages. The site sits on a staging address until the owner approves it.
Rose Law Nevada
A Nevada law firm that came to us for a website. Staff update case results and testimonials in a private CMS without touching code, and a connected intake form feeds a lead pipeline the firm manages itself. See the before and after on our work page.
Questions people ask
Before you call.
Custom or off the shelf, how do we decide?
On the first call we ask what the software has to do and whether a product already does it. If a subscription covers the job, we say so and set it up. Custom makes sense when the product forces your team to work its way, or when what you need is not sold as a product.
Who owns the code?
You do. The source code lives in a repository your business owns, the hosting and cloud accounts are opened in your business's name, and the admin logins are yours. That means you can hire someone else to change it, move it to another host, or switch it off without asking us.
How much does custom software cost?
There is no rate card, because a small portal and a system that runs a dispatch office are different jobs. You describe the software, we send one fixed price and a schedule in writing, and nothing starts until you approve it.
What happens when something breaks after launch?
Fixing launch issues is part of the project. After launch, we can quote a support agreement that identifies the maintenance included and how additional work is priced. If you bought the build as a Project and stopped there, you hold the code and the accounts, and you can bring the fix to us or to anyone else as a quoted job.
Can you take over something someone else built?
Yes, and it starts with reading it. We ask for access to the repository and the hosting, write down what is there and what is missing, and tell you in writing what we would change. If the last developer stopped answering, we sort out access with the hosts and vendors first. The quote comes after that review, with a price you approve before we touch the code.
Related
Other work we do for Reno businesses.
Get in touch
Tell us what's wrong.
Tell us what the business runs on and where it breaks. We are in Reno, NV. Call (775) 993-0103 or email hello@beachintelligence.co.