Milwaukee has enough public micromobility information to design a sensible test, but not enough verified public evidence to promise e-bike rental demand. Start with a pilot, not a large purchase.
The city reports that its permanent dockless scooter program followed three pilot studies and more than 1.5 million scooter trips. Bublr Bikes also operates more than 100 docked stations across Greater Milwaukee. Those facts show an established mobility market, but they don't predict how many people will rent your e-bikes at your price.
Use local evidence to shape a test. Then let your own trip, cost, and reliability data decide whether to expand.
What Milwaukee's existing data can tell you
Public sources answer different questions. Keep those questions separate.
| Local signal | Useful for | What it cannot prove |
|---|---|---|
| Milwaukee's dockless scooter program | Understanding city oversight, operating zones, and a nearby micromobility price benchmark | E-bike demand, e-bike pricing, or profitability |
| Bublr's station network | Seeing where established bike-share service is available and how a docked model works | Demand for a dockless rental fleet |
| Milwaukee Open Data Portal | Finding transportation, neighborhood, street, and land-use datasets for site selection | A ready-made forecast of paid e-bike trips |
| Your own pilot | Measuring actual rides, repeat use, maintenance, and revenue | Full-year demand if the test covers only one season |
| National market reports | Framing broad category interest | Milwaukee customers, local costs, or local conversion rates |
The Milwaukee Open Data Portal is a useful starting point for mapping destinations and transportation patterns. Check each dataset's description and update notes before relying on it.
Third-party market reports can make the category look large. Their definitions and methods vary, so keep them out of the core business case unless you can verify the underlying methodology. Turns out, a modest local test is more useful than a dramatic national estimate.
Build a local demand case in five passes
A good demand study doesn't need to be elaborate. It needs to connect a specific rider, place, trip, and price.
-
Choose the first customer and use case. Decide whether you are testing visitor trips, short errands, commuting, event transportation, or recreation. A visitor may want a one-hour rental, while a commuter may care more about reliable access and a longer pass.
-
Select candidate zones from evidence. Use public data, existing bike routes, hotels, campuses, employment areas, attractions, and safe parking locations. Don't assume that the busiest place for pedestrians is the best place for bikes. Riders need a practical route and a legal place to finish.
-
Review existing service. Use the Bublr station map and the city's scooter program information to identify coverage, gaps, and operating constraints. Existing service can reveal competition and partnership opportunities. It can also reveal locations where parking or sidewalk management may be sensitive.
-
Ask potential riders before buying equipment. A short survey should ask where the person would start, where they would go, how long the trip would last, what they would pay, and what would stop them from renting. Collect responses from people who could actually use the service, not only from friends or general online audiences.
-
Write a testable hypothesis. For example: "Visitors staying near Zone A will pay for an e-bike trip to destinations in Zone B during afternoon and evening hours." Include a proposed price, operating hours, and a measurable success condition.
The hypothesis matters. Without one, a pilot becomes a collection of rides with no clear business decision attached.
Design a pilot that answers operational questions
A five-to-ten-bike pilot can test placement, customer support, charging, locks, and payment flow without tying up the budget for a full fleet. It is a test size, not a Milwaukee demand benchmark.
Run the pilot long enough to capture normal operating problems. A two-to-four-week trial can expose workflow failures, but it cannot represent every season. Milwaukee weather and seasonal travel patterns make a warm-weather result especially easy to overread.
Keep the first test controlled:
- Use the same or closely matched bike models.
- Start in two or three defined zones rather than spreading bikes everywhere.
- Test one clear price structure before adding discounts.
- Give every bike a unique ID and record every status change.
- Log failed unlocks, late returns, damage, battery swaps, retrievals, and refunds.
Place bikes where staff can inspect them regularly. A slightly smaller service area is easier to manage than a broad map with long retrieval times.
Measure the following from the first ride:
| Metric | Definition | Decision it supports |
|---|---|---|
| Trips per available bike-day | Completed paid trips divided by available bikes and service days | Whether placement and supply generate use |
| Revenue per available bike-day | Ride revenue divided by available bikes and service days | Whether the fleet earns enough before overhead |
| Ride minutes per bike | Total paid minutes divided by bikes in service | Whether customers use the bikes for meaningful trips |
| Repeat rate | Customers who complete more than one trip during the test | Whether use extends beyond one-time curiosity |
| Downtime | Hours a bike cannot be rented because of repair, charging, or software problems | Whether the fleet is operationally dependable |
| Support contacts per trip | Customer issues divided by completed trips | Whether the rider experience scales |
| Damage and theft incidents | Count and cost by bike and zone | Whether the operating model is financially practical |
Define utilization before you discuss a target. A claim such as "70% utilization" is not useful unless you say whether it means moving time, available hours, trips per day, or revenue. Use the same definition throughout the pilot.
Price against a local benchmark, then test the economics
The city's dockless scooter page lists a $1 unlock fee and $0.40 per minute. It also describes automatic discounts in certain program zones. That is a useful local reference point, but it is a scooter price, not an established e-bike tariff.
Bublr uses a different station-based model. Its site says its e-bikes provide pedal assistance up to 15 mph and that pass purchases can include a $10 temporary hold. Neither detail should be copied automatically into a dockless rental plan.
Set a candidate price, then test how riders respond. You can compare a standard rate with one controlled variation, such as a time-of-day discount or a longer pass. Avoid changing the unlock fee, minute rate, service area, and operating hours at the same time. You won't know what caused the result.
Use this basic calculation:
gross revenue per ride = unlock fee + (paid minutes x minute rate)
Then subtract payment fees, refunds, charging labor, maintenance, retrieval, insurance, permits, software, customer support, and expected damage. A busy fleet can still lose money if each trip creates too much handling work.
To be honest, the first pricing test is often a learning exercise. Don't present an introductory discount as proof that the regular price works.
Confirm Wisconsin and Milwaukee requirements before purchase
Legal classification should come before the purchase order. The bike's motor, pedals, assist speed, throttle behavior, equipment, and intended facility can all affect the analysis.
Start with WisDOT alternative transportation resources. Then check current Milwaukee requirements through Milwaukee.gov and request written guidance when the answer affects fleet specifications or operating permission.
The draft's reference to a 2018 Wisconsin proposal is historical, not current authority. You can read the 2018 Urban Milwaukee proposal summary, but don't use it to approve a fleet. Secondary sources also conflict on some class and trail questions.
Before launch, document answers to these questions:
- Does each planned model qualify as an electric bicycle under the current Wisconsin definition?
- Which class does each model meet, and does its throttle or pedal-assist behavior match that class?
- Are there age restrictions for the class or facility you intend to use?
- Where may the bikes operate, and are there local restrictions on sidewalks, trails, or specific routes?
- Does Milwaukee require a permit, operating agreement, parking plan, geofence, or other approval for this rental model?
- What insurance limits, rider terms, incident procedures, and records does the city or insurer require?
- Do sales tax registration or other business registrations apply to your transactions?
Keep the model specification sheet, serial-number list, classification research, insurance certificate, rider agreement, privacy notice, and city correspondence together. A rental business needs an auditable file, not just a verbal answer.
Set your own minimum rider age only after checking current law and your insurer's conditions. A business policy can be stricter than the legal minimum, but it should be written clearly and applied consistently.
Build the operating system around the bike
A rental fleet is a service workflow. The app is only one part of it.
For a small pilot, a spreadsheet and payment dashboard may be enough if one person can reconcile them every day. As the fleet spreads across multiple zones, use software that can track:
- bike IDs, serial numbers, locations, and service status;
- payments, refunds, deposits, rider agreements, and trip history;
- geofences, parking rules, speed settings, and remote lock status;
- maintenance tickets, battery status, inspection history, and parts;
- incident reports, customer messages, and exportable financial data.
Choose tools by workflow rather than by feature count. A platform that cannot export clean trip and revenue records will make the pilot harder to evaluate.
Create a simple operating rhythm. Check each bike before deployment. Inspect brakes, tires, steering, lights, controls, lock hardware, and app connectivity. Remove a bike from service after a crash, serious complaint, abnormal battery behavior, or failed safety check.
Battery procedures must follow the manufacturer's manual. Chemistry, pack design, charger type, and enclosure change the correct charging and storage instructions. Don't mix chargers, use a damaged pack, or create a generic temperature rule for every model. Store and charge batteries in a controlled area that matches manufacturer instructions and local fire guidance.
Milwaukee's seasonal conditions also affect the plan. Decide in advance when to reduce service, collect bikes, pause rentals, protect batteries, and handle weather-related refunds. One successful summer test won't establish winter economics.
Decide when to scale
Set decision gates before the first ride. Otherwise, a busy weekend may push you into an unnecessary fleet purchase.
| Result from the pilot | Sensible response |
|---|---|
| Strong repeat use and positive contribution after operating costs | Consider adding bikes in the best-performing zones |
| Good demand but high downtime | Fix charging, parts, software, or staffing before expanding |
| Rides occur only during discounts | Recheck the regular price and customer segment |
| One location performs while others do not | Concentrate the fleet instead of expanding the map |
| Frequent damage, theft, or parking complaints | Change equipment, controls, terms, or location |
| Low use after testing placement and price | Pause, reposition, or change the customer segment |
| Unclear legal classification or city permission | Stop deployment until the issue is documented |
Scale in measured batches. Add bikes only when the existing fleet has enough data to justify more supply and the service team can support it.
Common questions from operators
Is Milwaukee scooter data enough to forecast e-bike rentals?
No. It can show that the city has experience with shared micromobility and can provide a local price reference. E-bike demand still needs its own test.
Should I copy the city's $1 unlock and $0.40-per-minute scooter price?
Use it as a comparison point, not a recommendation. E-bikes may have different trip lengths, costs, customer segments, and parking needs.
Are five to ten bikes enough?
They can be enough to test workflow, placement, and early customer response. They are not enough to prove full-year demand across Milwaukee.
Can I rely on a 2018 e-bike law summary?
No. Treat it as historical context only. Verify current Wisconsin and Milwaukee requirements through official sources and qualified legal advice.
What should I do first?
Open the Milwaukee Open Data Portal, review the city's Dockless Scooter Program, define five pilot metrics, and request written compliance guidance before ordering bikes.