Skip to main content

For businesses in San Francisco–Oakland

Connected business software for
San Francisco–Oakland.

Review a legacy system alongside its content, data and integrations. Choose a maintainable first change and a practical path through the dependencies.

Detroit-based design and engineering. Remote collaboration around your team.

A useful first decision

Which parts of our custom system are worth retaining, and what must change together?

We work with businesses in San Francisco, Oakland and the wider San Francisco–Oakland–Fremont market from our Detroit base. Start with the task, the people who need the result and the systems already involved. The project can focus on one capability or combine them where the work calls for it.

Your first review should make the next investment easier to judge. A focused scope can include:

  • A legacy-system and integration inventory
  • A retain/repair/replace recommendation
  • A migration and first-change verification plan

Three connected capabilities

A clear offer.
A working system.

Choose the work that solves the problem. Each service has its own scope, evidence and way to review the result.

01

Custom software

Custom software

Map the existing code, data and connections before choosing modernization or replacement. Trace a representative task through those dependencies and select a useful change that can be tested on its own. Record migration, recovery and handover decisions before retiring a dependency.

Working software demonstrationInspect a rules-based source lookup with an exact excerpt, a missing-source stop and an out-of-scope refusal. These fixed examples make the application’s decisions visible.

02

Websites and search

Websites and search

Review useful content, URLs and customer tasks before changing the platform. Separate public content from platform-specific behavior, and keep the destinations, forms and custom functions supporting a customer task in the migration scope alongside the new page design.

Owned websiteExplore Butler Agency’s service-to-inquiry journey and technical search setup. The walkthrough shows the site you are using and the decisions behind it.

03

AI and workflow automation

AI and workflow automation

Review the processes depending on the old system before adding a new connection. Identify its source, format, permissions and exception owner rather than relying on undocumented output. Keep transfers and approval rules understandable, and review any AI feature within the same information and operating boundaries.

Design reference · owned demonstrationThe same deterministic lookup illustrates source handling and human review. A language-model implementation needs its own task-specific evaluation; the demonstration supplies a concrete pattern to discuss.

Collaboration and handover

Review real work.
Know what you own.

We agree a practical review schedule, the working version you will inspect and who on your team approves each decision. Your team supplies authorized access, business rules and content; we bring the design and engineering needed for the agreed result.

The proposal brings deliverables, investment, dependencies, ownership and support together. For a website, review the pages, mobile journey and inquiry connections. For software or automation, check permissions, expected results and failure handling with representative examples before choosing the next step.

Questions before we talk

Can a redesign keep our existing integrations?

We review what each integration does, how it is accessed and which parts depend on the current platform. The proposal identifies what can be retained, updated or replaced and how the connected journey will be checked.

Can you improve our existing website or software?

Yes. We start by inspecting what you have, the problem you want to solve and the parts worth keeping. The recommendation can be a repair, a focused integration or a rebuild, with the work and review steps agreed before implementation.

How would we work together remotely?

Butler Agency is based in Detroit. We agree meeting times, review points and the people who can approve the work around your team. Shared working versions and written decisions give your reviewers a concrete way to check progress. Any on-site work would need its own agreement.

Who maintains the system after launch?

The proposal sets out ownership, licensed components, access, documentation and the handover. We can discuss ongoing maintenance or a handover to your team. Hosting, third-party services and support responsibilities are agreed as part of that arrangement.

Your business in San Francisco–Oakland

What would make the next project worthwhile?

Tell us about the website, application or workflow you want to improve. Bring the goal and the constraints; we can work through the technical choices together.