TXTWRK Addresses - Share an Address with Community / Startups / Individuals


Full Report (Pre-Build Release)


TXTWRK is building a system that turns physical locations into structured, shared, time-based assets, giving shop fronts a face lift, right up to seeing creature comforts fulfilling them and making new community glow zones!

This is not a listing tool.
This is not a booking platform.

This is infrastructure.

---

The Problem We’re Solving


Across the UK — including places like Derby — thousands of units sit empty because:
•Rent is too high for one person
•Risk is too concentrated
•Flexibility is too low
•Contracts are too rigid

Real Costs (Ground Reality)


Type of UnitMonthly CostYearly Cost
Standard town unit£3,500 – £6,500£42,000 – £78,000
Prime retail (shopping centres)£7,000 – £12,000+£84,000 – £144,000+
That model is broken for modern startups and communities.

---

The TXTWRK Solution


We split space by time and function.

Instead of:

> 1 shop → 1 tenant

We enable:

> 1 shop → multiple users → structured access → shared cost

---

System Overview


1. Address Layer


Users create and verify real locations:
•Address name
•Street + postcode
•Location hierarchy
•Map pin

This becomes a controlled, verified asset.

---

2. Opportunity Layer


Owners create opportunities tied to an address:
•Description
•Type (owner / landlord / manager)
•Who can apply
•Requirements

Then they define options inside the space.

---

3. Space Options (Core Engine)


Each address can contain multiple usable layers:

Example OptionPurpose
Main HallRetail / general use
KitchenFood prep
Media RoomContent / production
Storage AreaInventory
Each option includes:
•Price (hourly or monthly)
•Minimum contract length
•Facilities included
•Security coverage
•Electricity rules
•Commission rules (if selling happens)

---

4. Application Flow


Users don’t just “book” — they build structured usage.

They:
•Select address
•Select option(s)
•Set date range
•Build timetable
•Attach identity (character profile)
•Attach info (contact / media)
•Submit purpose

---

5. Approval + Payment


Owner:
•Reviews request
•Approves or declines

User:
•Pays manually (PayPal / bank transfer)

System:
•Confirms payment
•Writes timetable records automatically

---

What Gets Created


Every successful application becomes:
•A timetable record
•Linked to an address
•Linked to a user
•Linked to identity + info
•Visible across the platform

---

Profile Integration


For the User


Shows:
•SHARED ADDRESS
•Their operating times
•Their identity + purpose

For the Owner


Shows:
•Normal timetable entries
•Multiple users layered into one space

---

Maps Integration — Places Open


TXTWRK already has a live discovery layer.

Shared Address feeds directly into it.

Users can discover:
•Active shops
•Who is operating there
•What times they’re active
•What type of activity it is

Filters include:

•Store name / @username
•Street
•Time range
•Place types
•Categories (safety, hygiene, culture, etc.)

---

Multi-User Locations (Key Shift)


Each location can now contain:
•Owner
•Hosts
•Multiple startups
•Community groups
•Individuals

All structured by time.

This creates layered locations instead of single-use buildings.

---

Financial Model


Example Breakdown


ScenarioValue
Shop rent£5,000/month
Users10
Cost per user£500/month
---

Contract Structure


ElementStandard
Payment cycleMonthly
Minimum3 months
Payment methodPayPal / Bank
ConfirmationManual
---

Refund Logic


Simple and controlled:
•If owner shuts space → remaining time refunded fairly
•Otherwise → contract stands

Refunds are manual to prevent abuse and maintain control.

---

Electricity Model


Users declare:
•Devices
•Usage hours
•Estimated load

Owners define:
•Included usage
•Threshold
•Overflow cost

---

Passive Selling Layer


Two modes:

ModeDescription
Set HoursUser operates physically
Always OpenOwner sells on behalf
Example:
•Owner processes sale
•Takes 5% commission
•User earns without being present

---

Security & Trust


Each opportunity can define:
•Security coverage
•Insurance requirements
•Fire & safety standards
•Facility access
•Operational limits

Addresses are verified before sharing.

---

Why This Works


Because it fixes all 3 core problems:

ProblemSolution
High costShared across users
Low utilisationTimetable-driven usage
Access barrierStructured entry
---

System Strength (TXTWRK Advantage)


TXTWRK already has:
•Address engine
•Timetable system
•Profile system
•Map discovery
•Category filtering
•Identity layers

Shared Address connects all of them.

---

The Bigger Vision


TXTWRK is building:

A programmable layer for physical space

Where:
•Locations are structured
•Time is controlled
•Access is flexible
•Discovery is live

---

Mission

•Repurpose 10,000 empty shops in Britain
•Enable startups without huge capital
•Activate local economies
•Turn unused space into opportunity

---

Final Position


TXTWRK is not competing with listings or booking platforms.

We are defining:

The future of location technologies.

---

Why TXTWRK Is Ahead (Summary)

•It tracks time inside places, not just places
Everyone else shows locations. TXTWRK shows who is there, when, and doing what.
•It turns one shop into multiple opportunities
Others = 1 tenant.
TXTWRK = multiple users sharing space properly.
•It’s built on infrastructure, not features
Timetables + addresses + identity = core system, not add-ons.
•Maps are live, not static
You don’t just see a shop — you see activity, people, and timings.
•It unlocks real-world access
Not likes, not posts — actual physical space people can use.
•It’s hard to copy
Others would need to rebuild their whole system around time + space.

---

Bottom Line


TXTWRK doesn’t just show the world.

It organises how the world is used.