PartySound — shared music rooms
A live service for parties: create a room, invite guests by code or QR, and everyone hears one queue in sync.
Our part: Our own product: we built it, launched it and keep it running.
Service
Custom web applications and internal tools
A service your customers use, or an internal tool that saves your team hours: we build the interface, the server side and the deployment, and keep it running. Our own PartySound and a ticketing platform for an event organizer are live examples.
Who it's for
- Businesses that sell, book or serve customers online
- Teams buried in spreadsheets, documents and manual routines
- Anyone who needs a first working version of a service
Tasks we take on
- A web service or a client portal with real-time features
- A Telegram bot for sales, tickets or notifications, with an admin panel
- Importing, checking and reporting on documents and spreadsheets
- Connecting your systems through an API
- Taking over and finishing an existing service
What you get A working service that people use: interface, server side and deployment.
Scope of work
What the work can include
- Interface: a web app or PWA, a Telegram bot
- Server side on ASP.NET Core or Node.js with PostgreSQL
- Real time: WebSockets, SignalR, WebRTC
- Deployment to a server with HTTPS
- Support after launch, if agreed
What the estimate depends on
- The number of screens and user roles
- Integrations and payments
- Load and real-time requirements
- Hosting and support
What helps us start
- Who uses the system and what they do in it
- What exists today: spreadsheets, an old system or nothing
- The integrations you need
- Examples of services you like
Cases
Party Tickets — event ticketing
An event organizer in Da Nang needed to sell tickets through Telegram and check them quickly at the door.
Our part: We built the platform and maintain it for the client.
Site Agent — the AI assistant on this site
The assistant on this page is Site Agent, our product: it answers from the site's content and hands over to a person.
Our part: Our own product: server side, widget, operator console and deployment are ours.
See it working
Open PartySound (opens in a new tab)
Create a room and open it on a second phone: one queue, playback in sync.
How we start
- 01
Describe the task
Use the form, the chat, or write directly by email or Telegram. No ready specification is needed: a few sentences about what should work and for whom are enough to start.
- 02
We clarify the details
We read the request and ask only what affects the next step: a new or existing solution, platforms, constraints, materials.
- 03
We agree on the next step
Depending on the task, this is a consultation, an estimate, a prototype or development. Format, cost and timing are agreed individually before any work starts.
What affects cost and timing
- The number of screens, roles and scenarios
- Integrations, payments and notifications
- Real-time features
- Hosting, monitoring and support
There is no price list: the cost is confirmed after we look at the task, and format and timing are agreed before work starts.
Questions
Can you take over an existing service?
Yes. First we look at how it is built and what state it is in, then propose what to fix first.
Do you build mobile apps?
PartySound runs as a web app and as an Android version installed from an APK. Whether a native app or a PWA fits better is decided per task.
Where will it run?
On your server or ours — agreed per project. Our own services run on our Linux server behind nginx.
Can you work under an NDA?
Yes, by agreement. Document automation for a private company in 2024–2025 was done under an NDA, so it has no public demo.
Not ready to order development?
Start with a consultation: we sort out the question first, with no obligation to order the work.
Contact
Tell us about your task
A few sentences and one way to reach you are enough.