Customers see where their order stands without phoning you
Many of the calls a business takes are one question: where is my order? When customers can look that up themselves, the phone rings less and your staff finish what they started.
In practice: each job gets a status your team updates as part of the work. The customer opens a private link or signs in and sees that status, with the next step and a date if you set one.
People can book, order or pay online at any hour
Your customers decide to buy in the evening and on Sundays, when your door is locked. If they can place the order or pay the invoice right then, you start the next morning with work already on the list.
In practice: we build the ordering, booking or payment screens around how you sell. Card payments run through a payment company in your name, so the money goes straight to your account and never passes through ours.
The form stops a mistake before it becomes a bill
A wrong quantity or a missing phone number is cheap to fix while the person is still typing. It gets expensive after the order is packed and billed. Good forms catch the slip at the keyboard.
In practice: each field checks what is typed against rules you set, and the form will not save until the problems are fixed. The message says what is wrong in plain words, next to the field.
| The mistake | What the form does | What your staff see |
|---|---|---|
| A required detail left blank | Refuses to save until it is filled in | The empty field is marked with a short note |
| A delivery date in the past | Compares the date with today | A message asks them to pick a later date |
| The same customer entered twice | Looks for a matching name or phone number | The existing customer is offered before a new one is made |
| A hand-typed price that does not match the list | Fills the price from your price list | The price appears by itself and only a manager can override it |
Work keeps moving when the person who knows it is out
If one employee carries the whole schedule in their head, a sick day turns into a scramble. When each job lists its stage and its notes, whoever is in that morning can pick it up.
In practice: the app shows a list of open work with the latest note on each line. Handing a job to someone else is one action, and the new owner sees everything written about it so far.
Each person opens only the screens their job needs
A driver does not need payroll figures and a part-time clerk does not need to delete customers. Limiting what each login can open protects private details and keeps honest mistakes small.
In practice: you tell us the roles in your business and what each should be able to read or change. Those limits are enforced by the database itself, so hiding a button is never the only protection.
Your old records come with you on day one
Nobody wants to launch a new tool and then retype years of customers. Your history has value, and the app should open with it already inside.
In practice: we take an export from your current sheet or software, match its columns to the new fields and load it. You get a list of any rows that did not fit, so you decide what happens to them.
You are free to hire a different developer later
A business should never be stuck with one developer because that developer holds the keys. If we stopped working together, another team should be able to open the code and carry on.
In practice: the code sits in a repository your business owns, and the hosting and database accounts are registered to you. We leave written notes on how the app is put together and how to release a change.
Before a first call about a Kinston build
You do not need a specification. These notes get us most of the way.
- The question customers phone you with most often.
- What customers should be able to do online without your help.
- The entry mistakes that have cost you money.
- A list of roles in the business and what each should see.
- Where your customer and order history lives today.
Our service area
Service-area overview.
Tell us which calls you would like to stop taking.
Describe what your customers ask for by phone and what your staff look up to answer them. We will sketch what a status page or an ordering screen would involve for your business.
Book a free consultationOn the project call, we’ll discuss the problem, your existing tools and what TDAT should take off your hands. Then we can define the scope and next steps.
Or call (919) 289-1231
Questions before we start
Where is your team, if you have no Kinston office?
In Goldsboro. We have no office or employees in Kinston. Calls and screen sharing cover most of the work, and because Kinston is close we are glad to meet in person when that helps.
How is a build priced?
Each build gets its own written quote, because the price follows the work. Before that there is a free consultation, and for jobs that need a closer look, the Diagnostic: a written plan at a fixed fee that is credited to the build.
Do customers have to download something to check a status?
No. A status page opens in the browser on any phone or computer. A separate app from the app stores is possible, and we only suggest one when there is a clear reason for it.
Is it safe to take card payments through an app you build?
Card details are entered on screens run by the payment company, so they never touch the app we build or your own computers. The payment account is yours, and you can see every charge in it.
How long before customers could use it?
That turns on how much the first version covers. A narrow start reaches customers sooner than a wide one. The schedule is written into the plan once we have agreed the scope with you.