Startup Tucson × ReThread · Pilot proposal · July 2026

Start with the work.

Before deciding what a content series should look like, we propose starting with a focused pilot inside Startup Tucson. Your team would experience the ReThread process firsthand, we would work together on one meaningful challenge, and the work itself would show us what may be useful to share with other founders.

See how the pilot could work ↓

Our recommendation

Pilot with Startup Tucson first. Design the series second.

We began this conversation around a potential content series. Rather than choose its format before we know what the most useful story is, we recommend beginning with the experience the content would eventually need to capture.

Startup Tucson would take part in a focused ReThread pilot. That gives your team a direct view of how the process works, creates useful work inside Startup Tucson, and helps both teams see which parts of the experience may matter to other founders.

At the end, we decide together whether there is a series, what it should focus on, and which format would serve the story best.

What we heard.

  • Startup Tucson and ReThread are interested in creating a content series together, while the subject and format are still open.
  • Startup Tucson is moving from broad reach toward a smaller, invitation-only group of roughly 100 founders who are actively working to grow.
  • Staff receive founder context through website registrations, event activity, email, office calls, text messages, mentor introductions, pitch competitions, and economic-impact follow-up. There is not currently one clear place to see that full history together.
  • Deciding who may be ready for deeper support depends on signals that are more nuanced than time in business or consistent revenue, including follow-through, coachability, participation, and how founders respond to introductions.
  • A meaningful amount of staff time goes to intake and triage, including repeated exchanges before a founder reaches the resource or program that best fits what they need.
  • The team has explored CRM-style and case-management tools, but has not found an option that neatly fits the combination of relationship history, program participation, and founder development it needs to understand.
  • Startup Tucson is also looking for year-round storytelling opportunities for TenWest and new ways to add value for active founders. Starting with the work would let the strongest lessons emerge from the experience instead of deciding them in advance.

Five stages. One contained problem.

Each stage reduces uncertainty before the next one begins.

  1. 01

    Understand

     Examine the people, workflow, systems, and workarounds behind the problem.

    Meet with the Startup Tucson team and trace how a founder moves from first contact through programming, referrals, deeper support, and impact follow-up. We will look at what happens across emails, calls, texts, spreadsheets, event registrations, and the judgment staff apply along the way.

    ReThread leads

    Interviews, workflow mapping, system inventory, and a clear account of the current state.

    Startup Tucson brings

    The people closest to the work, representative examples, and candid explanations of the workarounds.

    Stage output

    A shared problem map and a short list of assumptions that need evidence.

  2. 02

    Measure

     Establish a baseline and locate where the underlying friction creates the greatest impact.

    Review the data that already exists and define a small set of baseline measures. The aim is to understand where the symptoms are most visible, which potential causes are supported by evidence, and how we will know whether the eventual response helped.

    ReThread leads

    Data review, baseline design, evidence gaps, and a practical measurement plan.

    Startup Tucson brings

    Available records, current reporting needs, and judgment about where staff time is being lost.

    Stage output

    A baseline with confirmed measures, plus a clear note where the data is not yet available.

  3. 03

    Focus

     Prioritize the opportunities and choose one high-impact, well-defined problem.

    Present a prioritized opportunity list and agree on one starting point. The selection should sit as close as possible to a verified root cause, offer meaningful value if addressed, and be contained enough to learn from clearly. The specific problem and response remain open until the first two stages are complete.

    ReThread leads

    Opportunity framing, tradeoffs, a recommended first problem, and a definition of the most focused meaningful test.

    Startup Tucson brings

    Business judgment, resource constraints, privacy considerations, and the final prioritization decision.

    Stage output

    A brief naming the problem, user, success signal, exclusions, and acceptance criteria.

  4. 04

    Build

     Develop a focused working solution capable of creating value and learning.

    Based on what we discover, design and implement a focused response inside the current workflow. It may involve a process change, a better connection between existing information, or a lightweight tool. The form of the response follows the problem we confirm together.

    ReThread leads

    Solution design, implementation, testing, documentation, and transparent progress updates.

    Startup Tucson brings

    Fast feedback from the staff who will use it and access to the agreed test environment.

    Stage output

    A working pilot artifact with clear boundaries and a path for future decisions.

  5. 05

    Improve

     Compare the outcome with the baseline and decide what to keep, change, expand, or stop.

    Monitor the response in use, collect staff and founder feedback, and compare the outcome with the baseline. The closing review will separate what worked from what merely looked promising and make the next decision together.

    ReThread leads

    Outcome review, iteration where warranted, and a concise closing recommendation.

    Startup Tucson brings

    Usage context, feedback from the people involved, and the decision about continued ownership.

    Stage output

    A keep/change/expand/stop decision supported by evidence and documented learning.

How the pilot could work

01

Understand

Examine the people, workflow, systems, and workarounds behind the problem.

Trace how a founder moves from first contact through programming, referrals, deeper support, and impact follow-up. We will look at what happens across emails, calls, texts, spreadsheets, event registrations, and the judgment staff apply along the way.

ReThread leads
Interviews, workflow mapping, system inventory, and a clear account of the current state.
Startup Tucson brings
The people closest to the work, representative examples, and candid explanations of the workarounds.
Stage output
A shared problem map and a short list of assumptions that need evidence.
02

Measure

Establish a baseline and locate where the underlying friction creates the greatest impact.

Review the data that already exists and define a small set of baseline measures. The aim is to understand where the symptoms are most visible, which potential causes are supported by evidence, and how we will know whether the eventual response helped.

ReThread leads
Data review, baseline design, evidence gaps, and a practical measurement plan.
Startup Tucson brings
Available records, current reporting needs, and judgment about where staff time is being lost.
Stage output
A baseline with confirmed measures, plus a clear note where the data is not yet available.

How the pilot could work

03

Focus

Prioritize the opportunities and choose one high-impact, well-defined problem.

Agree on one starting point that is close to a verified root cause, meaningful if addressed, and contained enough to learn from clearly.

ReThread leads
Opportunity framing, tradeoffs, and a recommended first problem.
Startup Tucson brings
Business judgment, constraints, privacy considerations, and the final decision.
Stage output
A brief naming the problem, user, success signal, exclusions, and acceptance criteria.
04

Build

Develop a focused working solution capable of creating value and learning.

Design and implement a focused response inside the current workflow. It may be a process change, a better connection between existing information, or a lightweight tool.

ReThread leads
Solution design, implementation, testing, documentation, and progress updates.
Startup Tucson brings
Fast feedback from the staff who will use it and access to the test environment.
Stage output
A working pilot artifact with clear boundaries and a path for future decisions.
05

Improve

Compare the outcome with the baseline and decide what to keep, change, expand, or stop.

Monitor the response in use, collect feedback, compare the outcome with the baseline, and separate what worked from what merely looked promising.

ReThread leads
Outcome review, warranted iteration, and a concise closing recommendation.
Startup Tucson brings
Usage context, feedback from the people involved, and the ownership decision.
Stage output
A keep, change, expand, or stop decision supported by evidence.

A strategic boundary for the pilot.

  • Root cause firstUse discovery and evidence to distinguish the underlying cause from the symptoms appearing around it.
  • One high-impact problemChoose the most consequential problem that can be addressed responsibly within a focused pilot.
  • Focused responseBuild the most focused response capable of producing meaningful value and clear learning.
  • Contained and transparentKeep the work measurable, show decisions as they happen, and name what is explicitly out of scope.
  • Shared client portalGive Startup Tucson one place to see the current stage, working notes, evidence, open decisions, and next agreed move.
  • Commercial framing after scopeConfirm the pilot’s value, participation terms, and any scholarship framing only after the focused problem is defined.

The work stays visible.

To keep both teams working from one source of context, a shared portal will be provided. Key decisions, evidence, and next steps will have one place to land.

Field note 02 · EvidenceFind the source of friction
Field note 01 · KickoffExplore one founder journey
Working example
Startup Tucson Pilot
Illustrative working format
UnderstandMeasureFocusBuildImprove
This week

Map one founder journey from first contact to the right level of support.

What we learned

Capture the systems, human judgment, workarounds, and missing context in plain language.

Decision needed

Questions that require Startup Tucson’s judgment before work continues.

Next agreed move

One owner, one date, and a clear reason the next step matters.

ConversationEvidenceDecisions

The pilot ends with a choice.

  1. What changed in the selected workflow, and what did the team learn?
  2. Should the solution stop, continue as built, receive one more iteration, or expand?
  3. Which parts of the problem-solving process would be genuinely valuable to other founders?
  4. Should the collaboration become a video series, written field notes, a TenWest initiative, a referral partnership, an application-based scholarship, or something else?

Let’s continue the conversation in early August.

The next step is an in-person working session with the Startup Tucson team. We can use that conversation to look more closely at the challenges discussed, trace one representative founder journey, and determine whether there is a clearly defined problem worth taking through the pilot.