AI Workflow Implementation in Annapolis, MD

Both, depending on the engagement. The technical build itself runs remote — we're writing n8n flows, OpenAI prompts, and Cloudflare Workers code, none of which benefits from being in the same room. But for kickoff, the workflow audit interview, and the final handover and training, in-person works well for Annapolis-based clients. The drive from the DC side is short, and we've found that walking the office, sitting with the person who actually answers the inquiry email or assembles the proposal, surfaces details that never come up on a Zoom call. State agencies and Naval Academy contractors with security or facility access requirements: we're comfortable working under whatever escort or visitor protocol your office runs. For maritime clients on the water, we'll come to the marina or the office — wherever the workflow actually happens.

Yes, with the same caveat we apply to every state-procurement integration: eMaryland Marketplace doesn't expose a clean public API for vendor-side automation, so the integration layer is built around document export, structured email parsing, and the parts of the workflow that live in your internal systems — your CRM, your document library, your past-performance database. The automation does the assembly, deduplication, compliance pre-check, and routing. The submission itself stays in the procurement portal where the contracting officer expects to see it. If your firm is also responding to federal solicitations through SAM.gov, we've built that integration before and the same architecture extends cleanly. We'll map every data flow on paper before any credential changes hands, and your contracts officer signs off on the scope before we touch live systems.

Seasonal is actually the cleanest case for workflow automation, because the cost-benefit math is sharper. Your team is fine handling inquiry volume in January. They're underwater in May. The build targets the peak — a workflow that triages inbound, drafts quotes against your boat inventory and seasonal pricing, checks Dockwa or your internal calendar, and queues responses for a captain to review and send. We typically scope these for delivery before the season ramps, which for Annapolis means kickoff in January or February for an April go-live, or kickoff in late summer for the October boat show window. After the season, the workflow keeps running on lower volume; nothing to switch off. If you want, we can also wire in winter-only flows like off-season maintenance scheduling or refit project tracking that share the same automation layer.

For most state-agency and Naval Academy contractor work, the AI layer runs on enterprise endpoints with no-training, zero-retention contractual terms — typically Anthropic, OpenAI enterprise, or Azure OpenAI, where prompts and outputs are not used for training and are not retained beyond the request lifecycle. The signed zero-retention DPA is part of the engagement file. For workflows that touch CUI or anything more sensitive than ordinary business confidential, we'd scope a different architecture — likely Azure Government or AWS GovCloud — and we'd be honest with you up front if the workflow is a poor fit for off-the-shelf AI services. Not every workflow should be automated with a public LLM, and we'd rather tell you that during the audit than after the build. The audit deliverable explicitly maps which workflow steps can route through which trust tier.

From the $99 audit booking to a live workflow in production, the realistic window is four to six weeks for most Annapolis engagements. The audit itself takes about a week — intake call, workflow walkthrough, written report. If you decide to move forward, the implementation is two to three weeks: prototype in week one, connect your live systems in week two, testing and handover in the final days. We don't take more than one or two new builds at a time, so booking sits in real calendar order — if the audit lands in early May, the build typically slots into late May or early June. We'll be straight with you on the calendar at the audit stage, not at the contract stage. Compared with a generalist ai automation agency or a big ai consulting firm that bills by the hour and runs a discovery phase before anything ships, every Golden Horizons engagement is fixed price and the audit replaces the billable discovery theater. If you need something live before a specific date — a procurement deadline, the start of charter season, an audit committee meeting — say so on the first call and we'll tell you whether it's feasible.