Small teams without a project manager
Five to fifty people who need to know what is in flight and what is stuck, without hiring someone to run the tool. Boards, sprints and deadlines that stay useful when nobody is grooming them.
All systems
SuiteWright Task
Pre-liveProject management software for Cambodian teams — and you can pay by KHQR
Running on the pre-production environment — not yet in production.
Project and task management for small teams — boards, sprints, deadlines and who is doing what, with team chat, meetings and timesheets built into the same system rather than sold as three more subscriptions. Built for teams in Cambodia and ASEAN, so the monthly bill can be paid by Bakong KHQR or ABA PayWay without needing an international card.
Big project tools assume a project manager whose job is the tool. Small teams do not have that person. What they do have is a payments problem the international tools ignore: a Cambodian team paying a monthly subscription should be able to pay the way Cambodia pays.
So the gateway list is chosen by country — KHQR and ABA PayWay here, card via Stripe elsewhere — rather than offering everyone a card form and hoping. The task management underneath it is the part everyone builds; the payment routing is the part most leave out, and it is the part that decides whether a team here can actually buy the thing.
The second thing small teams do without is context. The work is on a board, the conversation about it is in a chat app, and the hours are in a spreadsheet that gets filled in from memory on the last day of the month. Putting the three in one system is not a feature list — it is the difference between an invoice you assemble and an invoice you print.
The board is the project, not a picture of it
A board that has to be updated to match reality is a second job, and it is the job that gets dropped first. Here the board is where the work actually lives — moving a card is the update. Projects, sprints and statuses are yours to name, so the columns match how your team already talks about work instead of how a tool thinks it should.
- Custom statuses per project — the columns are yours, not a fixed set
- Sprints with templates, so the next one starts already shaped like the last
- Labels, watchers and assignees, so the right people hear about the right cards
What is actually blocking what
"Why has this not moved?" is usually answered by asking three people. A task can depend on another task, carry its own checklist, and belong to a milestone — so the thing holding up a delivery is visible as a link between two cards rather than something someone remembers in a meeting.
- Dependencies between tasks, so a blocked card says what it is blocked by
- Checklists inside a task, for work that is one job but several steps
- Milestones and reminders, so a date arrives before it has passed
The chat, the meeting and the timesheet are in the same place as the work
Most teams run a project tool, a chat tool and a timesheet tool, and spend their time carrying context between the three. Here they are one system: the conversation about a task sits with the task, the meeting has notes and attendees, and the hours were logged against the work they belong to instead of being reconstructed at the end of the month for an invoice.
- Chat and notifications delivered live over a socket, not on a refresh
- Meetings with attendees and attachments, kept beside the projects they concern
- Time entries and timesheets, recorded against the task while the work happens
What it replaces
The jobs that eat the week
- Work tracked across a group chat, a whiteboard and someone's memoryOne board per project, where the current state is visible to everyone
- Paying for a project tool, a chat tool and a timesheet tool separatelyThe three in one place, on one bill
- Being unable to subscribe because the tool only takes foreign cardsPaying the monthly bill by KHQR or ABA PayWay, like everything else
- "What is everyone working on?" answered by asking everyoneA view that answers it without interrupting anybody
- Hours reconstructed at the end of the month for invoicingTime logged against the task while the work is happening
- A delay nobody can explain without three separate conversationsA dependency between two cards, showing what is waiting on what
Why it's built this way
The decisions that matter
A team in Cambodia can actually buy it
The gateway list is chosen by country rather than shown to everyone and hoped over. A team billing from Cambodia pays by Bakong KHQR or ABA PayWay; elsewhere it is card via Stripe. The task management underneath is the part everyone builds — being payable from here is the part most tools leave out, and it is the part that decides whether a team can subscribe at all.
No project manager required
Large project tools quietly assume someone whose actual job is maintaining the tool — grooming the backlog, fixing the workflow, chasing people to update cards. Small teams do not have that person. This is built for teams who need the board to stay useful without a full-time administrator behind it.
Three tools, one bill, one place
Chat, meetings and timesheets are not integrations here, they are part of the same system as the tasks. That matters most at month end: the hours are already attached to the work they were spent on, so an invoice is a report rather than an afternoon of remembering.
Live, not on refresh
Chat messages and notifications arrive over a socket as they happen. A comment on a task, a mention, an assignment — the person sees it while it is still relevant, rather than the next time they happen to reload the page.
Permissions that match your shape
Roles and permissions are yours to define, and people can be organised by team, department and position rather than one flat list of users. So the person who should not see the finance project does not see it, and you set that rather than asking us to.
One company can never see another's
Every request is scoped to your organisation before it reaches the database, and a query that arrives without one attached is refused rather than quietly answered. Your projects, tasks, messages and hours are yours alone.
Who it is for
One platform, four kinds of institution
Agencies and studios billing time
Firms where the hours are the invoice. Time logged against the task while the work happens, so the month end is a report rather than a reconstruction — and the client's work is separated by project rather than by memory.
What's inside
Module by module
Projects & boards
A board per project with columns you name yourself, where moving a card is the update rather than a second job afterwards.
Tasks, checklists & dependencies
Assignees, due dates, labels, watchers, comments and attachments — plus checklists inside a task and dependencies between tasks, so a blocked card says what it is waiting on.
Sprints & milestones
Sprints with reusable templates so the next one starts shaped like the last, and milestones that give a set of tasks a date worth hitting.
Custom statuses
The columns on the board are per project and yours to define, because "in review" means something different in every team.
Team chat
Threads and direct messages delivered live over a socket, in the same system as the work being discussed.
Meetings
Meetings with attendees and attachments, kept beside the projects they concern instead of in a separate calendar tool.
Timesheets & time tracking
Time entries recorded against the task while the work is happening, and timesheets that add up without anyone reconstructing a month.
Notifications & reminders
Mentions, assignments and approaching dates, delivered live rather than discovered on the next page load.
People, teams & permissions
Users organised by team, department and position, with roles and permissions you define rather than inherit.
Announcements & bug reports
Announcements for the whole organisation, and a place for people to report a problem that is not a task.
Activity log
A record of what changed and who changed it, so a question about a card two months later has an answer.
Subscription & billing
Plans, invoices and the payment rails that suit where you bill from — Bakong KHQR and ABA PayWay in Cambodia, card elsewhere.
iPhone app
Tasks, projects, chat, meetings, the calendar and timesheets on iOS, for updates that should not wait for a laptop.
Questions
Frequently asked
Can we pay for it from Cambodia?
Yes, and it is the main reason this exists. The subscription is paid by Bakong KHQR or ABA PayWay for Cambodian teams, and by card through Stripe elsewhere — rather than showing everyone a card form and hoping they have an international card.
Do we need a project manager to run it?
No. Big project tools assume someone whose actual job is maintaining the tool. This is aimed at teams who do not have that person — boards, sprints and deadlines that stay useful without a full-time administrator.
Does it replace our chat and timesheet tools too?
That is the intent. Chat, meetings and timesheets are part of the same system as the tasks, so time is logged against the work it belongs to instead of being reconstructed at month end for invoicing.
Can we keep different clients or teams apart?
Within your organisation, work is separated by project, team and department, and permissions decide who sees which. Between organisations the separation is absolute — every request is scoped to yours before it reaches the database, so another company can never see your projects.
Is there a mobile app?
There is an iPhone app covering tasks, projects, chat, meetings, the calendar and timesheets. An Android build is not released yet.
How much does it cost?
It depends on team size. Tell us how many people need access and you will get a straight number rather than a quote process.
Is SuiteWright Task available yet?
It is pre-live — built, deployed and running on our pre-production environment, but not yet in production. Get in touch to see it running or to talk about being an early pilot.
How it is licensed
A subscription, starting with a 30-day trial
SuiteWright Task is multi-tenant software you subscribe to, not a one-off build. Every new workspace starts on a free 30-day trial of the Pro plan. There is no permanently free tier — when the trial ends you move to a paid plan or the workspace is suspended, with your data kept intact for a grace period so subscribing brings it back.
- 30 days
- Free trial on the Pro plan
- No free tier
- A paid plan after the trial, or suspension
- KHQR & cards
- Bakong KHQR and ABA PayWay locally, cards internationally
Not open for signup yet. SuiteWright Task is Pre-live — running on the pre-production environment, not in production for any customer, so there is no trial to start today. Ask for a demo and we will tell you when signup opens.
See SuiteWright Task on your own data
A demo runs through your actual workflow rather than a scripted tour — bring the awkward parts.