Skip to content
Wisxia
Menu

What you can build

Everything below is what Wisxia builds today, not a roadmap. Each one starts the same way: you describe it, and it asks what it needs.

tools

Tools that run on Wisxia — the thing that stores and works your records: the people you serve, the things you track, the activities you manage. Trackers belong here too: GPS units and dash cams on your vehicles, people and things, where they are and where they have been.

websites

Websites — branded, and for the people you serve. Staff work in Wisxia itself, so this is the outward-facing end only.

mobile apps

Mobile apps — the same again for phones and tablets: branded, and for the people you serve.

What a built thing can be asked to do

Not a list of separate products — these are things you ask the thing you built, in the same conversation you built it in.

  • create, update, delete, query and search records
  • import and export data
  • schedule, assign, and set who is allowed to do what
  • publish, collaborate, message, and run campaigns
  • analyse, visualise, forecast, recommend, diagnose, optimise and simulate
  • generate and translate content
  • process documents, images, audio and video
  • maps, routes, GPS tracking and dash cams
  • APIs, automations, AI agents and integrations
  • security, compliance, payments and settings

Added when you ask for it

None of these arrive by default. Ask for the ones you want, when you want them.

  • reports and dashboards
  • reminders and scheduling
  • messaging the people you serve, or your team
  • who's allowed to do what
  • payments
  • importing and exporting data

And what it can’t do

Said plainly. Planning around a maybe is worse than planning around a no.

  • 3D scenes, AR/VR, virtual walkthroughs and spatial experiences
  • training your own AI model
  • certifying that what you built satisfies a regulation

Start with a sentence

Describe the thing you wish you had. You can stop at any point, and what you have said is not lost.