I offer coworking space website design to help operators present their workspaces, plans, and contact options. You work directly with me, Dicky Ibrohim, a web engineer and technical lead, to organise that information so prospective users can understand the space before asking about a visit or availability.
The website can provide a reference for approved photographs, amenities, access hours, and locations. WhatsApp or email can serve as the initial contact route. Seat reservations, payments, member accounts, and door access controls are not included by default in this informational website service.
Explain the spaces through the needs they serve
Someone looking for a desk to work alone has different questions from a team seeking a meeting room. I help organise the options you actually offer so visitors can compare spaces without having to infer their purpose from interior photographs.
Where available, shared desks, dedicated desks, private offices, and meeting rooms can each have their own description. Commercial names can remain, with an explanation of what users may access. Capacity, amenities, and conditions come from the operator; a space that is not ready is not presented as an active option.
For example, the same photograph of a shared area might illustrate both a day pass and a monthly membership. The room is the same, but access hours or included amenities may differ. I help connect that image to the appropriate plan details rather than repeating the entire amenities list under every option.
Photographs should show conditions relevant to the offer. Captions can distinguish work areas, meeting rooms, and shared facilities. Material showing members, computer screens, or documents needs to be selected with the appropriate rights and permissions. An illustrative image should not serve as evidence of the actual premises.
Make each plan's inclusions understandable
A plan page helps visitors assess suitability when its units are clear. Pricing per person, desk, room, hour, or membership period answers different questions. Published prices follow the actual terms, including additional charges and the duration of any promotion.
I can help organise plan information around the following questions:
- Which desk or room can someone use, and for how many people?
- On which days and during which hours does access apply?
- Which amenities are included, subject to allowances, or charged separately?
- Does a meeting room require a separate request even when the plan includes an allowance?
Building opening hours, staffed hours, and member access rights need to be distinguished where they differ. A statement about 24-hour access for one plan should not extend to all users. Likewise, a meeting room's presence does not establish that every plan includes its use without a fee or confirmation.
If the operator also offers mail handling, that service can be described separately according to the actual offer. I do not turn a correspondence address into a promise that customers automatically obtain a business licence or may use the address for every legal purpose. This article concerns the presentation of workspaces, rather than company formation services.
Help visitors find the location and request a tour
Once a space looks suitable, a prospective user needs to know how to get there. The building name, floor, entrance, visitor reception instructions, and visiting hours can be more useful than the area's address alone. For multiple locations, each page should point to the correct branch's contact and amenities.
A map link can open a destination checked with the operator. Google's Maps URLs documentation explains links to places or directions. Using them helps open the intended destination; it does not establish the entrance's accessibility, guarantee a journey time, or improve Maps rankings.
I help distinguish buttons such as “Ask about plans” and “Request a tour” according to the conversation they initiate. W3C's guidance on link purpose explains that a link's purpose should be understandable from its text or context. Visitors can tell the operator their preferred location, space type, group size, and timing through the chosen channel.
That request still needs a response. Sending a message does not confirm a tour, hold a seat, or activate membership. If a reservation system already exists, the website can link to it after its destination and flow have been checked. Availability calendars, payment integrations, and membership management require a separate discussion of functionality.
A custom website reflects how spaces, plans, and branches relate
A custom website allows information to follow the way your coworking business serves its users. We can discuss a route where visitors choose a location first, then explore the spaces and plans offered there. This helps avoid a general amenities page that makes every branch appear to provide the same services.
Suppose one branch adds private offices while another continues to focus on shared desks. The structure can develop to make the new option easy to find without obscuring existing services. The visual identity can remain consistent while each location's content reflects its circumstances. Further changes are assessed for technical requirements, time, and cost.
A SaaS website builder, an application operated by its provider, may also suit your needs if its layouts and editing facilities are appropriate. Pricing follows its plans and terms, including free options where available. Check limits on location pages, editor accounts, media, and integrations, along with content rules and policy changes. A withdrawn feature or revised allowance could affect how your team updates plan information.
With me, you can discuss the connections between information and the editing work directly. For example, a change to a branch's hours needs to be considered alongside plans that refer to access at that branch. Management facilities follow the quotation; simultaneous updates or synchronisation with operational systems are not assumed. Some platforms also support your own domain, so that is not an exclusive advantage of custom development.
Control over content is distinct from rights to the code and development tools. Source code is not handed over automatically; it may require a separate offer and is not always available. Accounts, licences, supplied files, and the rights to use them need to be clarified before work begins.
If a platform suffers an outage, discontinues a service, or closes, copies of text and photographs may not be enough to run the website elsewhere. GOV.UK's guidance on technical lock-in discusses service benefits alongside exit considerations. Migration of a custom website also depends on access, available backups, rights, compatibility, and cost. Discussing these matters early helps you assess the options; it does not promise freedom from vendors or interruptions.
An engineer assesses what AI-generated work can miss
AI can help draft a coworking website, but polished wording may not reflect the operator's offer. Building opening hours, for example, could be wrongly presented as access rights for every member. A photograph of a meeting room might also produce a description implying that its use is included in every plan. OWASP's explanation of AI misinformation addresses outputs that sound credible despite being inaccurate.
I direct and review AI-assisted work against the information your coworking team provides. An engineer's work can include matching spaces to plans, reviewing presentation on different devices, and checking each location's contact destination within the agreed scope. Conflicting operator information needs clarification; AI does not determine membership terms.
The benefit is having someone with whom to discuss the consequences of a change. When a new plan launches, we assess which sections need updating and whether buttons still reach the right staff. AI-assisted code also requires review and functional testing appropriate to the work, rather than being treated as ready because the page opens successfully.
Material supplied to AI tools is selected according to need and permission. Member lists, door access records, and identity documents are unnecessary for creating a sample plan page. OWASP's guidance on sensitive information provides a reference for assessing data risks; each tool's terms still need consideration.
Building the website yourself with AI can be reasonable if you can assess the output, test functions, and maintain it. My service offers that discussion and technical work within an agreed scope. Using AI during development does not mean visitors will use a paid AI feature on the finished website.
Clear content responsibilities keep the website useful
Identify who approves changes to plans, hours, photographs, and contacts. Editing requirements can be discussed early so the facilities built match how the team works. A single location may need only a concise page; a business with several branches needs more detailed distinctions. For one offer, a landing page website may be an alternative worth discussing.
I consider how ordinary visitors will read the information on phones, laptops, and desktops. Workspace photographs should support a decision without hiding prices or important conditions. SEO, security, and speed foundations are usually discussed as part of the quoted work. Google's SEO Starter Guide is a reference, but there is no promise of indexing, rankings, AI recommendations, or more members.
If analytics are needed, the purpose of measurement should be clear. Public pages, visitor statistics, prospective members' messages, technical logs, and administrator access concern different kinds of information. A provider may see particular data depending on architecture, permissions, settings, and policies; technical access does not automatically grant permission to use it for other purposes.
We can discuss the data collected, recipients, retention, and export options. GOV.UK's cloud guide for the UK public sector also addresses provider management and data access. Choosing custom development does not remove the data flows associated with any hosting or analytics provider used. A WhatsApp click is different from a completed tour or active membership; establishing that connection requires appropriate additional data, rather than an inference from page statistics.
Website costs follow the information and functions involved
The number of locations, space types, languages, available photographs, editing facilities, and agreed integrations affect the work. Photography, regular content updates, and reservation systems should be specified if required. The website development price does not also determine subscription charges for your coworking operations software.
When comparing individuals, agencies, and platforms, examine what each offer includes: content organisation, functional checks, editing access, licences, and assistance. A lower price alone does not explain quality or suitability. Speaking directly with me helps establish priorities suited to your material and budget.
Recurring costs may include the domain, hosting, media, licences, and support. For platforms, consider introductory or promotional prices, renewals, usage, extra features, and exit costs. Rates can increase under the applicable terms and notice arrangements. Comparing custom development with a platform requires equivalent needs and periods; custom is not promised to be the cheapest option.
I also have experience addressing malware and can discuss a more favourable offer for clients needing relevant assistance. Eligibility, scope, and fees depend on the case. OWASP A06:2021 addresses vulnerable or outdated components; maintenance remains necessary because new vulnerabilities and reinfection are possible. Any agreed support follows its written scope and does not promise a permanently trouble-free website.
Start with one location and a clearly defined plan
Prepare photographs you may use, space types, plan terms, access hours, the address, and the operator's contact details. One location with complete information can provide a basis for discussing the website structure, including how to add other locations if needed. Members' personal data and door-system access are not required for the initial conversation.
Once the requirements are understood, we discuss the proposal, outstanding material, pre-launch checks, and agreed access and assistance. You can read my profile, then send your coworking website requirements through the contact form or email hello@dickyibrohim.com. The discussion starts with how prospective users choose your space and what they need to know before contacting the operator.
Frequently asked questions
Does this coworking website include reservations and payments?
The initial scope covers spaces, plans, locations, and contact information. It can link to an existing system after checks. Seat reservations, payments, member accounts, and door controls require a separate functional scope.
Can it present several branches and membership plans?
That can be discussed based on the available information. Spaces, amenities, access hours, plans, and contacts need to relate to the correct location. Page counts and editing facilities follow the agreed work.
Does a tour request reserve a seat immediately?
No. A WhatsApp or email request still needs the operator’s response. Tour timing, desk availability, and membership depend on the operator’s confirmation process.
What happens when plans or access hours change?
Approval and update responsibilities should be discussed early. Editing may cover plans, hours, photographs, and contacts according to the quotation. Synchronisation with operational systems is not automatically included.
What determines the website cost?
Locations, space types, languages, content readiness, editing facilities, and integrations affect the build cost. Domains, hosting, media, licences, and assistance may create recurring costs. Send an outline of the spaces and requirements through the contact form to discuss scope.
Is source code supplied, and can the website move anywhere?
Source code is not automatically included and is not always available for handover. Accounts, content rights, licences, backups, and supplied files need clarification. Migration depends on access, rights, destination compatibility, and cost; it is not a promise of compatibility with every host.
