Solutions
Custom systems for Virgin Islands operations.
FruitStack designs software around the people, processes, infrastructure, and constraints that already exist. Not around a generic product template that assumes your organization works like one somewhere else.
Booking and scheduling
Reservation platforms for beaches, tours, activities, appointments, facilities, and events.
A booking system is really a capacity system with a payment attached. The hard part is never the calendar: it is what happens when a boat leaves Red Hook late, when a group of twelve arrives as a group of nine, when high season changes the price, and when someone at the gate needs to know in two seconds whether this person paid.
What usually goes wrong
- Double bookings across phone, email, and walk-up
- Capacity guessed at rather than enforced
- Waivers signed on paper and stored in a box
- No-shows absorbed instead of measured
- Seasonal pricing maintained by hand
Capabilities
- Live availability and hard capacity limits
- Deposits, balances, refunds, and receipts
- Digital waivers signed before arrival
- Staff check-in that works on a phone
- Seasonal and group rate rules
- Occupancy and revenue reporting
Example workflows
- Guest books and pays → waiver sent → signed before arrival
- Walk-up added at the gate → capacity updates everywhere
- Cut-off reached → remaining slots close automatically
What changes
- One list everyone is working from
- Capacity that holds without someone policing it
- Payment status visible at the point of check-in
Relevant industries — Hospitality, tourism operators, government facilities, marine charter
Booking software in the U.S. Virgin Islands — costs, platforms, and when custom is worth it
Transportation and rentals
Reservation, rental, and dispatch tools for taxis, ferries, charters, fleets, equipment, and vehicles.
Dispatch is a real-time problem across St. Thomas, St. John, and St. Croix, where arrivals shift constantly. The system has to hold an accurate picture of who is where, what has been assigned, and who is still waiting, and it has to stay usable from a driver's phone at a dock with two bars of signal.
What usually goes wrong
- Dispatch run from a whiteboard and a phone
- Manifests that do not match what the captain has
- Late flights discovered when the passenger calls
- Rental damage disputed with no record
- Deposits tracked in a separate spreadsheet
Capabilities
- Dispatch, assignment, and driver status
- Passenger manifests and check-in
- Fleet, equipment, and inventory records
- Rates, seasonal rules, and surcharges
- Photo inspections and damage records
- Automatic customer notifications
Example workflows
- Inbound flight moves → pickup shifts → passenger notified
- Vehicle assigned → driver sees the manifest on their phone
- Unit returned → inspection photos attach to that rental
What changes
- A dispatch picture that matches reality
- Fewer calls asking where the vehicle is
- Damage and deposits with evidence attached
Relevant industries — Taxi and tour operators, ferry and marine, equipment rental, resort transport
Portals and internal systems
Secure portals that give employees, customers, vendors, and leadership the information they need.
Most internal chaos is an access problem. The information exists, but getting it means asking the one person who knows where it is, and on a small island team that person is often on leave. A portal gives each group exactly what they are entitled to see, and gives the organization a record of who looked and who approved.
What usually goes wrong
- Requests routed through whoever answers first
- Approvals living in email threads
- Vendors calling for status updates
- Documents scattered across drives and inboxes
- No audit trail when a decision is questioned
Capabilities
- Role-based access and permissions
- Document upload, versioning, and retention
- Approval workflows with a visible queue
- Customer and vendor self-service
- Activity logging and audit trail
- Leadership dashboards
Example workflows
- Request submitted → routed to the right approver → logged
- Vendor uploads a document → it files against their record
- Staff member leaves → access removed in one action
What changes
- Fewer interruptions for the person who knows everything
- A defensible record of who approved what
- Onboarding and offboarding that take minutes
Relevant industries — Resorts, government agencies, property management, professional services, nonprofits
Government technology
Public information systems, civic-data platforms, case tools, and internal government workflows.
Public technology in the U.S. Virgin Islands carries a different obligation: the record has to be findable, the source has to be visible, and a correction has to be shown rather than quietly made. Internally, the same system needs to move a case through the people who have to touch it without losing the trail.
What usually goes wrong
- Records that exist but cannot be found
- Public information published as scanned PDFs
- Case status known only to the person holding the file
- Reporting assembled by hand each cycle
- No visible history when a figure changes
Capabilities
- Public-facing searchable records
- Source documents linked to every figure
- Internal case tracking and routing
- Role-based permissions across departments
- Scheduled reporting and exports
- Visible correction and revision history
Example workflows
- Record published → indexed → searchable with its source attached
- Case opened → routed → status visible to the applicant
- Figure corrected → correction notice published alongside it
What changes
- Fewer records requests, because the record is already public
- A case trail that survives staff turnover
- Reporting that leaves on schedule
Relevant industries — Territorial and municipal agencies, authorities, boards and commissions, public institutions
GIS and property intelligence
Interactive mapping connected to parcels, infrastructure, property information, and operational data.
A map is only useful when it is wired to the records behind it. The work is usually in the reconciliation: USVI addressing does not match mainland formats, parcel identifiers on St. Thomas, St. John, and St. Croix come from different sources, and the infrastructure layer was last updated by someone who has retired.
What usually goes wrong
- Parcel data separated from the records that explain it
- Addresses that will not match between systems
- Infrastructure positions held in one person's memory
- No way to filter a map and export the result
- Layers that go stale with no update process
Capabilities
- Parcel, zoning, and boundary layers
- Infrastructure and asset overlays
- Address crosswalks and matching
- Service territory definitions
- Search, filter, and spatial queries
- Filtered exports and location-based reports
Example workflows
- Search an address → resolve to a parcel → open its records
- Filter by zoning and status → export the matching set
- Asset moved in the field → layer updated the same day
What changes
- One map the whole organization trusts
- Addresses that reconcile with other systems
- Exports produced in minutes rather than days
Relevant industries — Government agencies, utilities and infrastructure, real estate, planning and permitting
Integrations and reporting
Custom databases, system integrations, scheduled reports, and workflow automation.
Often nothing new needs to be built. The systems already exist and simply do not speak to each other, so a person becomes the integration: exporting, reformatting, pasting, and reconciling. On a small territorial team that person is expensive, and they are the single point of failure.
What usually goes wrong
- The same data typed into two systems
- Monthly reports rebuilt by hand every month
- Exports that break when a format changes
- Failed records disappearing silently
- Historical data too messy to use
Capabilities
- Data cleanup and normalization
- System and API integrations
- Payment, calendar, and accounting connections
- Scheduled reports and automated delivery
- Workflow automation and triggers
- Failed-record visibility and retry
Example workflows
- Booking taken → pushed to accounting → reconciled overnight
- Report scheduled → generated → emailed to the list
- Sync fails → the specific record is flagged, not dropped
What changes
- Hours a week returned to the person doing it manually
- Reports that arrive without anyone remembering
- Failures you find out about from the system, not the client
Relevant industries — Any organization running more than one system, which is most of them
Before you scope anything
Not sure what to call the system you need?
That is normal. Start by showing us what the team does today, where information gets lost, and what takes too much time. We will help define the system from there.
Start here
Tell us what the operation needs to do.
You do not need a specification. A screen recording of the spreadsheet is usually more useful than a requirements document, and it takes you two minutes.
How every engagement runs