ANCIENT CITY AIST. AUGUSTINE, FLORIDALet’s talk ↗

ANCIENT CITY AI / WHAT WE CAN BUILD TOGETHER

Give the work
a better way through.

A lead should reach the right person. A job should have a clear next step. Your team should know how to use the tools you pay for.

01 / KEEP THE CONVERSATION MOVING

Lead & quote
follow-up.

$2,500 one-time · defined implementation

An inquiry comes in during a showing or while the crew is on a job. Give it a place to land, someone to own it, and a follow-up that doesn’t rely on memory.

Explore the sample workflow ↗

What you get

  • One organized intake and opportunity view in the agreed tools.
  • Owner assignments, next actions, and reminder rules.
  • Response templates your team can review and use.
  • Written instructions, one team training session, and 30 days of fixes to the agreed setup.

Before we build

Confirm software compatibility, lead sources, team ownership, permitted communication channels, and stop rules.

How we judge it

Test capture, duplicate handling, routing, reminders, and follow-up stopping. Track how many open leads have an owner and a next action.

One location, one workflow, up to two existing software systems. Sending automation or AI drafting must be expressly scoped; it is not assumed in the fixed package. Software and messaging costs are separate.

Discuss your follow-up process ↗

02 / FROM ACCEPTED WORK TO FINISHED WORK

Job & paperwork
coordination.

From $4,500 one-time · scoped before work begins

Give the office, field team, and project owner a shared way to see what’s ready, what’s missing, and who needs to act.

What you get

  • A repeatable process for one type of job.
  • Project folders, required-document checklists, and status tracking.
  • Clear handoffs and reminders for missing information or work ready for billing.
  • Written instructions, one team training session, and 30 days of fixes to the agreed setup.

Before we build

Agree on job stages, document requirements, who can access records, and which person confirms completion.

How we judge it

Test incomplete jobs, missing documents, and handoffs. Compare time spent finding status and the delay between completion and billing readiness.

One location, one workflow, up to two compatible existing systems. Large migrations, custom applications, and AI document extraction are separate scope. Your professionals retain technical and approval decisions.

Discuss your job workflow ↗

03 / MAKE THE TOOLS USEFUL TO THE TEAM

Practical AI
workshop.

Custom scope team size, tools, and agenda agreed first

Your team doesn’t need a tour of every new AI app. It needs practice with the tasks it actually does—and a clear understanding of what to check.

A focused working session

  • Choose two everyday tasks: a follow-up draft, a meeting action list, or an internal checklist.
  • Practice using fictional or approved examples in an agreed tool.
  • Review outputs against the source, check missing information, and decide what needs human approval.
  • Leave with reusable task instructions, a review checklist, and a named owner for continued practice.

Before we schedule

Confirm the audience, approved accounts, data rules, task examples, and facilitator preparation. Software licenses are separate.

How we judge it

Participants complete a practice task and explain how they verified it. Agree on a follow-through check with the team lead.

Available as a separately scoped engagement. This is practical team instruction, not a certification, legal review, or a promise of measurable savings.

Plan a team workshop ↗

04 / AN IDEA TO TEST WITH YOUR DOCUMENTS

Company knowledge
assistant pilot.

Feasibility first separately quoted pilot · not a ready-made product

Could your team find an answer in its approved procedures and job guides without hunting through folders? We can start by assessing one small, internal use case.

What we would test

  • One user group, one document collection, and a defined question set.
  • Whether answers can be traced to the right source and version.
  • Whether the system declines questions the documents cannot answer.
  • Access boundaries, answer quality, running cost, and the effort needed to keep sources current.

What must be established

Document ownership, permissions, an approved AI provider, account and usage budget, hosting, and a person to maintain the collection.

The pilot decision

Proceed, revise, or stop based on documented tests. Production rollout and ongoing operation require a separate agreement.

This capability is in development. We have not established a production client deployment. No autonomous professional advice, eligibility decisions, or access to unapproved client records.

Discuss whether a pilot fits ↗

NOT SURE WHICH PROJECT COMES FIRST?

Start by understanding
one part of the business.

The $750 Business Operations Review walks through your process and tools, identifies bottlenecks, and delivers a prioritized plan with one recommended first project. The full review fee is credited toward an implementation booked within 30 days.

Build a first-project brief ↗See how delivery works ↗