Skip to content
Talavine Consulting · Work directly with Scott Crossen

Let’s build software your business can count on.

AI can get a first version running quickly. It takes an experienced developer to design for the way your business works, review what AI builds, and test what happens when things go off script.

A design decision in practice “Send website inquiries to our CRM.”
  1. AI helps build the connection.Start with a working form and a CRM record.
  2. We decide how it should behave.What if the contact already exists, or the CRM is down?
  3. We test the messy cases.Submit twice and simulate an outage. Check that the request is saved and the team gets one follow-up task.
See the integration example

I’ve spent more than 30 years building business software for banks, manufacturers, and service companies. My work spans software architecture, database design, and user interfaces, all in service of making real business processes easier to run and automate.

A prompt can describe the result you want. A working system also needs decisions about which records to trust, who can change them, and what people should see when something goes wrong. I’ll work through those decisions with you, then review and test what we build against the way your team actually works.

How I put that into practice at Talavine

Here’s what I’ve been building, from a workspace that keeps the evidence close to an open-source tool for working with AI on code. The screenshots use demo data.

Talavine Matters workspace with a client renewal brief and its source records

Talavine

I built a desktop workspace that brings client email and notes together so you can open the records behind an AI answer.

See the client workspace
Talavine CRM deal pipeline organized by stage

Talavine CRM

I built a shared workspace that keeps customer records, deal stages, and follow-up tasks together so the team can see where a deal stands.

Explore the CRM

What we could work on together

Integrations

Give every inquiry a next step.

Connect forms and inboxes to your CRM, match requests to existing contacts, and make sure the right person knows to follow up.

How we’d test it

Send a duplicate request, try one with missing details, and simulate a CRM outage. Check what gets saved and when a teammate needs to step in.

AI workflows

Give your team a briefing they can check.

Pull recent emails, meeting notes, and open questions into a client briefing that links to the original records.

How we’d test it

Give the workflow an old deadline and a newer correction. Check that the briefing uses the current date and flags any unresolved approvals.

Custom software

Take a prototype into everyday use.

Bring a spreadsheet or an AI-built prototype. We’ll work out what to keep and design the data and screens around the people doing the job.

How we’d test it

Import a sample of your existing records and walk through a real handoff. Check that the next person sees what’s due and has the right access.

Let’s start with one job worth fixing.

  1. 01

    Walk through the job together.

    We look at who does the work, which tools they use, and where they get stuck.

  2. 02

    Agree on the first version.

    We settle the scope, cost, and what a successful first run looks like before work starts.

  3. 03

    Try it and hand it over.

    We check it against real examples and walk through how your team will run it and handle exceptions.

Talk to Scott

What would you like to build or improve?

A few lines are enough. Tell me what you’re trying to do, what you’ve tried so far, and what you’d like to happen next.

Email Scott about your project support@swarmmarshal.com
Subject “Talavine consulting inquiry”