For 10–100-person CPA firms
Busy-season capacity without another hire.
Gulf & Ponte reduces the preparer time spent collecting, chasing, organizing, and preparing client documents.
One reviewed workflow across the systems your firm already uses.
One workflow. 30 implementation days. Fixed fee agreed before implementation.
Human review remains where judgment matters.
The problem
Your staff should prepare returns — not manage PDFs.
Documents arrive through portals, inboxes, and upload links. Staff update request lists by hand, chase missing items, rename and organize files, and prepare the same information for review again and again. Each task is simple. Together they consume busy season.
Gulf & Ponte turns that fragmented handling into one reviewed workflow.
The outcome
Fewer manual touches between document request and workpaper.
A Gulf & Ponte workflow can help your firm:
- Keep document status aligned across approved intake routes.
- Send routine missing-item follow-ups on an agreed schedule.
- Prepare documents and extracted fields for review.
- Route approved documents to the correct workpaper destination.
- Surface exceptions instead of letting failures disappear.
Where firms start
Start with the bottleneck that hurts most.
- 01
Client document intake
Bring approved intake routes into one visible process, so staff stop checking several locations.
- 02
Missing-item follow-up
Cut the time spent reviewing request lists and writing routine reminders.
- 03
Workpaper preparation
Prepare documents, fields, and exceptions for human review before filing.
The exact workflow depends on your systems, permissions, and review requirements.
Why this is not software
Software gives your staff capabilities. It does not create your firm’s workflow.
Your portal, practice-management system, inbox, tax software, and document store each handle part of the process. Manual work accumulates in the gaps between them.
Gulf & Ponte builds the reviewed workflow between those systems — without replacing the tools your staff already knows.
- Start with one measurable operational problem.
- Document the workflow so your firm can operate it.
Seats are not workflows.
How we start
Prove one workflow before expanding.
One practical question: can this workflow reliably reduce manual handling in your firm?
- Scope
- One agreed workflow
- Duration
- 30 implementation days
- Fee
- Fixed before implementation
- Acceptance
- Defined in writing
Systems are named before we build. Implementation begins once access and approvals are in place, and ends with staff training and written documentation.
What the first 15 minutes identify
- Where document handling consumes the most staff time
- Which systems are involved
- Whether the workflow is narrow enough to pilot
- Whether Gulf & Ponte is a fit
You will leave with a clearer definition of the workflow, the main system constraints, and whether a fixed-fee pilot is worth considering.
If it is not a strong fit, Yared will say so.
Who builds it
You work directly with the person building the workflow.
A one-person practice led by Yared Asefa in Seattle. Yared maps, builds, tests, and documents each workflow directly, so scope and accountability stay with one person.
About Yared and the engagement modelFit
Is this a good fit?
Good fit
- A 10–100-person CPA firm.
- Staff lose meaningful time to document handling.
- Existing software handles pieces of the process but not the whole workflow.
- A partner or operational owner can sponsor the pilot.
Probably not a fit
- You want to remove preparer or reviewer judgment.
- You want an open-ended AI strategy engagement.
- No one inside the firm can own the workflow.
Questions
What partners ask first.
Do we have to replace our existing software?
No. The work is built around the systems your firm already uses. Connection options depend on the permissions and vendor terms involved.
Can you connect to our specific tax stack?
Possibly. The first call identifies whether your systems offer a reliable, approved connection method. No integration is promised before those constraints are reviewed.
What can be proven in 30 implementation days?
Operational behavior: intake, routing, review, logging, and exception handling. Longer-term capacity outcomes may need a larger production sample.
How is sensitive information handled?
The deployment and access model is documented before production use, with external providers and data movement made explicit for your firm and its counsel.
Security, data flow, and §7216 reviewFind the first workflow worth fixing.
Bring the document process that hurts most during busy season. Fifteen minutes is enough to tell whether it is worth pursuing.
Do not send taxpayer documents, return information, credentials, or other client-confidential information.