How it works

The pipeline

Every night, a scheduled task on your ComputerEase server reads your data through CE's own database driver, using a dedicated login that only reads. It writes one file per table, plus a manifest that fingerprints every file.

The files upload to a landing zone in your Microsoft tenant. Before anything is written, a load step checks every file against the manifest and a fixed contract of expected tables and columns. If anything doesn't match, nothing loads, yesterday's data stays in place, and you get an alert. A night that would suddenly wipe out a large share of a table is refused, and a failed load retries on its own the next morning.

From there, readable views translate CE's codes and quirks into plain names, and those views feed Power BI and your AI agents.

The process

1. Week 0

   Fit call

   Thirty minutes, free. How is your ComputerEase hosted, which modules do you use, and what do you want to see? You leave with a straight answer on whether this fits.

2. Within a week

   Quote

   We take a short look at your setup and send a written scope with one fixed price.

3. Week 1

   Discovery

   We inventory your CE database: which tables hold real data, which columns are sensitive, and how your company uses custom fields and codes.

4. Weeks 1 to 3

   Build

   Server setup, cloud landing, the load step, readable views and data checks. Dashboards and agents follow in the See and Ask packages.

5. Before go-live

   Reconcile

   Your controller compares key numbers against the same screens in ComputerEase. Nobody relies on the data until they match.

6. Go-live, then 30 days

   Cutover and support

   We switch on the nightly schedule, watch every run, and support your team for 30 days.

Timelines depend mostly on how quickly access is granted. The build itself is measured in days, not months.

What we need from you

• Admin access to your Deltek-hosted dedicated server, where ComputerEase runs. See the FAQ on hosting if you're on Deltek's shared cloud.
• A dedicated ComputerEase login for the extract, with data-file access to the modules you want.
• A Microsoft 365 tenant with an Azure subscription. If you don't have an Azure subscription yet, we'll walk you through creating one in your name.
• One person who knows the numbers, usually the controller, for an hour or two of reconciliation.

Security

This is financial data. We build it the way we'd want our own built, and in one case, we did.

• Your tenant, your keys. Everything lives in your Microsoft tenant under your admin accounts. We work as guests, and you can remove us at any time.
• Reads only. The extract uses its own dedicated ComputerEase login and only ever reads. We never write to ComputerEase.
• No cloud passwords. The server signs in to your cloud with a certificate whose private key is stored as non-exportable on that machine, so there's no cloud password or secret to leak.
• A walled-off landing zone. The upload identity can reach only a separate landing area. It can't see your reporting data or your financials.
• Sensitive data stays home. Payroll, Social Security numbers, tax IDs, bank and routing numbers, and passwords are never extracted.
• Checked before it's trusted. Every file is fingerprinted and checked against the manifest and contract. A bad file stops the load instead of corrupting your data.
• Tiered access. Owner-level financials, like the GL and bank reconciliation, are kept apart from operational data. Report viewers get reports, never a database login.
• Audited agents. Each AI agent reads only the views it's granted, and every question it answers is logged.

What you keep

• The whole platform, running in your tenant under your accounts
• A runbook: how it runs, how to check it, what to do when an alert fires
• A data dictionary for your CE tables, written for your company's codes and custom fields
• The dashboards and agents from your package