A Software Company in Tampa for the Demo Due at an Ybor City Event

Updated November 2026 · Written and maintained by the Progression Agency strategy team

A small Tampa company reads a SOFWERX event notice on a Friday night, sees a problem it could solve with software it half has, and has a few weeks to turn that into something that works in front of the people who wrote the problem. SOFWERX, the Special Operations Command’s technology hub in Ybor City, runs events where companies show ideas and prototypes against a stated need. A software company in Tampa helping a firm like that builds the demonstration first and the product second. Progression is based in New York, builds for Tampa Bay companies remotely, and offers on-site sessions on request.

An event notice on a Friday night

The notice arrives in an inbox after dinner. Two screens of text, a problem statement in the middle, and a date near the bottom. The founder reads it twice and forwards it to the one developer on the team.

The notice above is a hypothetical, and it shows what every real one has in common: a stated need, a date and a short runway. What a firm does in the first weekend decides how much of that runway it keeps.

• Read the whole notice before replying to anyone.
• Write down the problem statement in one sentence of your own.
• Mark every date and who each one belongs to.
• Decide on Monday whether the firm is going to answer.

What a software company in Tampa should know about SOFWERX

DSIAC, the Defense Systems Information Analysis Center, reported on January 26, 2016 that U.S. Special Operations Command had opened its technology incubator, SOFWERX, in Ybor City, not far from SOCOM headquarters at MacDill Air Force Base. It described a 10,000 square foot open floor building meant to open new channels with the faster-moving private sector.

The SOFWERX site says the organization works with USSOCOM, other government bodies, academia and private entities. It lists current events to collaborate with USSOCOM on problems, past event summaries, external events and Tech Tuesday.

• Read the notice itself, not a post that summarizes it.
• Treat the site as the source for dates and rules.
• Ask the contacts on the notice about anything it leaves open.
• Do not rely on rumor about how events work.

Is every event open to every firm?

Each notice sets its own terms, and this page says nothing about who is chosen. Read the notice for who may take part.

Does the hub work only with large companies?

The site says it works with private entities, academia and others. A small firm should read the notice and decide for itself.

From notice to demonstration, step by step

Here is the path for a small firm, one row a step. The columns say what happens, the software decision that matters most, and what to leave out.

A demo that runs without a network

A room may have poor Wi-Fi or none. Build the demo to run from the laptop, with its data stored locally, and treat any connection as a bonus rather than a need.

Fake data that looks like the real thing

Use sample data with the shape, volume and mess of the real thing, so the demo behaves like the product would. Generate it yourself rather than borrowing anyone’s records.

What the demo should never contain

Never bring sensitive, controlled or classified information to a demo, and never put real personal data into sample records. If the notice says what may be shown, follow it. If it is silent, ask.

Reading completed event summaries first

The SOFWERX site says its completed event summaries give an overview of activities in support of USSOCOM, results, and potential paths forward. A firm can read them to see how the command described its own events.

• Look for the kind of problem each event stated.
• Look for what the summary says came out of it.
• Look at the paths forward, since they hint at what comes after a demo.
• Note how the summaries are written, and write your response plainly in the same register.

This is plain advice and not insider knowledge. A summary tells you what the command chose to publish, and not what any panel valued.

How many summaries are enough?

Read at least the last few that match your kind of problem. The goal is to understand the language and the level of detail, not to memorize them.

Building only what the problem statement asks

A demo wins attention by answering the question that was asked. One workflow, shown end to end, is more convincing than five half-working ones.

• Write the workflow as a list of screens or steps.
• Cut any screen that does not appear in the list.
• Keep everything else on a single slide titled what comes next.
• Test the workflow with someone who did not build it.

How do you decide what stays a slide?

If the problem statement does not mention it, it is a slide. If you are unsure, ask whether it helps the viewer understand the one workflow.

After the event: from demo to something that can be bought

A demonstration proves an idea. Software that a government customer can buy needs more: security work, documentation, support and a way to be installed and updated. That is a second build, and it should be planned as one.

• Write down what the demo mocks and what it would take to make it real.
• List the security and documentation work a buyer will ask about.
• Ask the notice’s contacts how follow-on work is handled.
• Do not assume a good demo leads to a contract.

Contracting questions go to the contacts named on the notice. This page covers the software, and it says nothing about procurement. For work with public agencies in general, see government software development.

What does the second build usually add?

Authentication, logging, packaging, an installation guide and a support plan. None of it is exciting, and all of it is what a buyer reads.

Tech Tuesday and the smaller first step

The SOFWERX site describes Tech Tuesday as a forum designed to identify and discover transformational levels of technology. For a firm that is not ready to answer a full event notice, it can be a smaller first step.

This page makes no claim about how any forum chooses what it hears. Read the site’s current description, and ask its contacts how to take part.

• Start with the forum if the product is early.
• Start with an event notice if you already have a working piece.
• Prepare a short, honest description of what the technology does today.

What should a first appearance show?

One clear capability, working, in a few minutes. A product tour is for later.

The demo kit checklist

Pack the kit a week before the event and test it from the bag. Each item on the card exists because a demo has failed without it somewhere.

Our software development company page describes how we plan and build.

Build decisions that change the demo

Four choices shape most small demos. None is right for every problem, and each should be made on purpose in the first week, not by default in the last.

The first choice matters most. A demo that depends on a connection fails the way demos fail, in front of the people it was built for. The second matters next: a demo that begins with the same data every time can be rehearsed until it is boring, which is the goal.

• Write the four choices on one page and keep it with the architecture page.
• Revisit them if the notice changes.
• Say aloud, in the demo, which choices were made for time.

When is a cloud service worth it?

When the problem statement is about a cloud service or a connected system. Even then, record a local fallback that shows the same workflow.

How polished should the interface be?

Clear enough that a viewer sees the workflow without explanation. Time spent on polish beyond that is time not spent on rehearsal.

What a demo build costs

A demo is a small build with a hard date. Here are the published US bands for software work. Hosting, licenses and security testing are on top.

Progression quotes after a written scope and publishes no Tampa price. For apps in the city, see app developers in Tampa.

Related services and guides

Pages that sit beside this one:

• Software development company
• Government software development
• App development company in Tampa
• Video production in Tampa
• Web design in Tampa

Frequently asked questions