App developer and web development for Fayetteville, NC businesses, built by a Goldsboro team.

Some businesses handle information that must not reach the wrong eyes, such as customer records and staff files. We build custom software for Fayetteville, NC businesses where access is controlled and every change is recorded.

Each person sees only what they are meant to see

In a shared spreadsheet, everyone who can open the file can read every row. In a properly built app, a login decides what a person may read and what they may change, record by record.

How it is done: access rules are written into the database, so they hold on every screen and for every kind of request. We then try to break them using test accounts, and fix whatever we get through.

You can prove who did what

If a customer, a partner or an inspector asks what happened to a record, a shrug is a poor answer. An app that logs each action lets you show the sequence of events with names and times.

How it is done: viewing, creating, editing and deleting can each be logged, depending on how sensitive the record is. The table lists questions the log can answer and where you would look.

Questions a change log answers
The questionWhere the answer isWhat you will see
Who changed this figure?The history on that recordThe user, the time, the old value and the new one
Who has looked at this file?The access list for the recordEach view, with the user and the time
What did this person do last week?The log filtered by userEvery action they took, in order
When was this record deleted, and by whom?The list of removed recordsThe deletion entry and a way to restore the record
Has anyone signed in from somewhere odd?The sign-in logEach sign-in with its device and rough location

The app does not buckle when everyone signs in at once

An app can run well in a quiet week and then fall over on the morning everybody needs it. Slow pages and failed saves at that moment cost you work and trust.

How it is done: before launch we load the app with realistic volumes and have many test users act at once. Weak spots are fixed, and monitoring is left running so trouble is noticed early.

A project that stalled gets across the line

Plenty of software projects stop short because the developer moved on or the AI tool hit its limit. The work already paid for can often be saved and completed.

How it is done: we review the code, the data and the hosting, and report what is sound and what is not. You get a written list of what remains, and we finish it in order of risk.

Wrong entries are stopped before they spread

One wrong entry can travel into invoices, reports and letters before anyone notices. Stopping it at the form is far cheaper than tracing it afterwards.

How it is done: the app checks formats, ranges and required fields as the person types. For values that matter a great deal, a second person can be asked to confirm before the record is accepted.

Approvals are recorded, with no chasing by email

Approvals handled by email are hard to find later and easy to miss today. Inside the app, a request waits in the approver’s list until it is answered, and the answer is kept on the record.

How it is done: you set which actions need approval and who may give it. The approver sees the details, decides and adds a note. The requester is told at once, and the log shows the whole exchange.

Your data can leave with you at any time

Controlled access should never mean the vendor controls you. Your business owns the database and can export all of it, including the logs, in a common file format.

TDAT builds from Goldsboro and has no office in Fayetteville, or on the Army post beside it. Our other projects are described on the Our Work page. Projects are run remotely. We travel to Fayetteville occasionally, when a meeting in person is needed.

Bring this to a call about your Fayetteville system

The more plainly you describe the rules, the better the plan.

  1. The kinds of records you hold and which are sensitive.
  2. Who should be able to read each kind, and who should change it.
  3. Any outside rules or contract terms about your data.
  4. Actions that should need a second person’s approval.
  5. Where the current system or the stalled project stands.

Our service area

Service-area overview.

How we can help

Tell us who should see what.

Describe the records you keep and the people who work with them. We will explain how access, approval and logging would be set up, and what it would take to finish anything already started.

Book a free consultation

On 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 TDAT based, and do you come to Fayetteville?

We are based in Goldsboro and do not have a Fayetteville office. Day-to-day work is remote. We make the trip for a meeting when the project needs one, and that is not often.

Can you build to a specific compliance standard?

Tell us which rules apply to you at the start, because they shape where data is stored and who may see it. We build to the requirements you name and write them into the scope. We do not claim certifications we do not hold.

What does software with access control cost?

Access control and logging add work, and how much depends on scope. Begin with a free consultation. The Diagnostic is a fixed-price written plan, credited to the build, and the build quote follows in writing.

Can you check an app we already have?

Yes. We can review an existing app for access problems and weak points, and report what we find in plain language. Whether to fix it with us is a separate decision.

How long does a build like this take?

Testing access rules properly adds time, and we will not skip it. The schedule comes with the written plan, after we know the roles, the records and the rules that apply to you.