Skip to content

AI services

AI for your paperwork, from the people who build the products.

Ademero makes software that reads documents and puts AI to work inside your document processes, and a team that sets it up for you. Here is what we do, where each part runs, and what a first project looks like on paper.

Three AI products, and the people who set them up and build on them.

01

Capture with CapturePoint 6

On your own Windows PC

Scan a stack or point it at a folder. It splits the pages into documents, works out what each one is, reads the fields and line items, checks the line-item math and files every document with a sensible name. It sets itself up from a folder of your sample documents and learns from every correction.

02

Paige, in the cloud

On Google Cloud

For documents that already arrive digitally. Send them in and get clean data back: Paige learns a document from a few samples, then pulls fields and line items and delivers them by download, SFTP or webhook.

03

Cortexa private AI

On servers you own

Our private AI platform, installed on your own servers. It is the AI inside CapturePoint 6 and Paige, and it connects to Content Central and Nucleus One, so AI can read and decide on documents, look up and fill in data, route work and move information between your systems. Your team gets a private chat app that signs in with your directory, and your developers get an OpenAI-compatible API, so no document goes to a public AI service.

04

Consulting and implementation

With our team

People who build these products sit with your team, follow the paper, pick the first project worth doing, then set it up, connect it to the systems you run, build custom AI tools around how you work, train your staff and stay with you after go-live.

What a first project looks like

Small, written down, and finished.

We would rather start with one paper-heavy job done well than a plan for everything. A first project names the documents, the fields, where they go and who is trained, and says just as clearly what is left out.

The example on the right is a common one: accounts payable. The same shape works for claims, loan files, student records or bills of lading.

Project scope · example

AP capture and approvals

Today

An accounts payable team gets supplier invoices two ways: on paper in the mail, and as PDFs saved to a shared folder. Clerks key each one into Sage 50, and approvals happen by email.

In scope

  1. 1.CapturePoint 6 installed on the AP clerk’s PC, with the job set up from a folder of last month’s invoices.
  2. 2.Fields: vendor, invoice number, invoice and due dates, PO number, subtotal, tax, total and every line item. Vendor names checked against your own vendor list.
  3. 3.Finished invoices exported to Content Central on your server with their fields, searchable by what they say.
  4. 4.An approval that starts each time an invoice arrives; invoices over a set amount go to a second approver; approvals waiting more than three days escalate.
  5. 5.Approved invoices exported to Sage 50 as bills, with an export status on each one.
  6. 6.Training for the clerks who scan and review and the managers who approve, then hand-over.

Out of scope

  • Matching invoices to purchase orders
  • Paying vendors
  • Changes to Sage 50 itself

You sign off

  • The list of document types and fields
  • The approval rules and amounts
  • Who is trained, and when
An example of how we write a first project, built from what the products do today. Not a customer story; every project is scoped with you.

What connects to what.

The part of implementation people ask about most. Each product has its own way in and out; this is the honest list.

ProductTakes documents fromSends them toFor your developers
CapturePoint 6TWAIN scanners; PDF, TIFF, JPEG, PNG, BMP and GIF filesYour folders, Content Central, SharePoint or OneDrive (work or school accounts), Google Drive, Dropbox, Nucleus OneA data file with every captured value, written next to each searchable PDF
PaigeThe documents you send inDownload, SFTP, webhook, or Content CentralSFTP and webhooks
Content CentralCapturePoint 6, Paige, scanning, Microsoft 365, Gmail or IMAP mailboxes, watched foldersQuickBooks Online and Desktop, Sage 50 (US and Canada), Sage X3, Workday, Epicor, Microsoft Dynamics CRM; AI from the Cortexa AI suite inside its workflowsAPI connections for document delivery and lookup; ODBC lookups from your own databases
Nucleus OneUploads, forms and CapturePoint 6Your team, your clients through client portalsA REST API and Zapier
CortexaYour team, your own apps, Content Central, Nucleus One, CapturePoint 6 and PaigeStays on your serversOpenAI-compatible chat, completion and embedding endpoints, plus OCR for PDFs and images

On a phone, swipe the table sideways to see every column.

How a project runs.

One team from the first call to the day it runs without us.

  1. Look at the work

    A free demo. We walk through where documents come in, who touches them and where they need to go, and run a few of your own documents through the products.

  2. Scope it in writing

    What is in, what is out and what you sign off, like the example above. We quote it once we both know what it covers.

  3. Set it up and connect it

    We install the products, set up the jobs and connect them to your folders, document library and accounting system.

  4. Train your team

    Hands-on sessions for the people who scan, review, approve and run it day to day.

  5. Stay with you

    After go-live the same team answers questions and adjusts the setup as your documents change. Call (863) 937-0272 or write to solutions@ademero.com.

Questions we hear first.

Do our documents have to go to the cloud?
No. CapturePoint 6 reads documents on your own Windows PC, Cortexa runs on your own servers, and Content Central runs in the cloud or on your own servers, your choice. Paige and Nucleus One run in the cloud for teams that prefer it.
Do we have to replace the systems we have?
No. Most projects connect to what you already run: your folders, SharePoint or OneDrive, your accounting system, or a document library you keep.
Can you build custom AI tools for us?
Yes. Our team builds custom AI tools and applications on the Cortexa AI suite and wires them into Content Central and our other products, around how you work. We start from products that already read documents every day, so you get a working result sooner and software we support.
What does a project cost?
It depends on what it covers. We scope it with you and quote it before any work begins. Talking it through, and a demo on your own documents, cost nothing.

Ademero has made document software since 2002 for 1,000+ organizations. Fortune 500 companies and government agencies review our security every year. See where your documents go with each product.

Bring a stack of your real documents.

On a free demo we run them through the products, map where they need to go, and tell you plainly what we would do first.