RReshape.
← All articles

Claude Connected to a Lender Pipeline: Getting Activity Data Behind a Single Sign-On Login

By Alex Regueiro · November 17, 2026 · 4 min read

A daily briefing is only as good as the data behind it, and the one in this build was missing activity-level data. The pipeline held that activity, but it sat behind a single sign-on login that Claude had not been able to reach.

This is common for mortgage loan officers and lending teams who keep their real work in a lender's pipeline system. Here is how we got Claude into it, and what we are rebuilding now that it is connected.

The situation

The owner of a lending office already had an operating hub in Claude that produced daily briefings. Those briefings lacked the activity-level data needed to make them accurate.

The activity-level data lived in the lender's own pipeline system. That system required a single sign-on login, so the briefing had no way to read it.

What was missing

Without activity data, a briefing can show where a deal sits but not what has happened on it lately. The operating hub had been working from the signals it could reach, and the activity signals were behind the login.

What we built

On the call we connected Claude to the pipeline through a dedicated browser profile that signs in with the office's single sign-on. The pipeline login lives in that profile, and the owner's everyday browser stays separate from it.

That connection unlocked the activity-level data the briefings had been missing. The next step is on our side: we are cleaning up the operating hub and rebuilding it around signals taken from the pipeline itself, and we are preparing a step-by-step daily usage flow so the owner knows exactly how to run it each morning.

  • A dedicated browser profile holds the pipeline login, apart from any personal browsing.
  • The operating hub is being rebuilt on pipeline-derived signals.
  • A step-by-step daily usage flow is being prepared for the next working session.
  • An AI notetaker is already configured, and two more team members need approval from the account holder so transcription can start across the team.

What changed

The rebuilt briefing had not run yet when the call ended, so we cannot report what it found. What changed is the reach of the system. Before, the activity-level data was out of reach. Now Claude can get to it, and the rebuild draws on it.

One item sits outside our hands. The notetaker is configured and connected, but the two added team members need access approved by the account holder, so transcription for the team waits on that approval.

Questions to ask before you connect an AI tool to a system behind a login

This section is advice, not a description of the client. Before you let any AI tool into a system that sits behind a login, work through these questions.

  • Which data do you actually need from that system? Name the fields before you connect anything.
  • Can you use a dedicated browser profile, so the connection stays apart from personal accounts?
  • Who owns the login and the seats? Put approvals with that person from the start.
  • What will the briefing do differently once it has the data? If the answer is vague, wait.

Frequently asked questions

Can Claude read a pipeline that sits behind a single sign-on login?

In this case, yes. We connected Claude through a dedicated browser profile that signs in with the office's single sign-on. That unlocks the activity-level data in the pipeline that the daily briefings had been missing.

Why use a dedicated browser profile for the connection?

It keeps the pipeline login in one place, apart from personal browsing. That gives the connection a clear boundary, which makes it easier to see which account it uses and what it touches.

What does activity-level data add to a daily loan briefing?

It adds what happened on each deal, not only where it sits. A briefing built on activity can point to files that have gone quiet or follow-ups that happened, which a list of stages cannot do on its own.

Has the rebuilt briefing produced results yet?

Not at the time of the call. The connection was made and the rebuild was about to start, with a daily usage flow being prepared for the next session.

If your pipeline data sits behind a login your tools cannot reach, book a 30-minute AI follow-up and reporting audit. We map which data your briefings need and how to connect it safely.