Piumal starts with the people using it, your existing tools and the part that needs to change. We check whether a setting or existing integration could solve it first.
A clear problem
02
Define a useful first step.
Agree one useful scope, the inputs you provide, completion checks, fees and dates.
An agreed brief
03
Build it. Review it together.
Work in visible stages, review the actual experience and check it against the brief.
Working software
04
Hand over with clarity.
Agree source, setup, usage and handover arrangements. Further development and support have their own scope.
A clear handover
A small Sri Lankan team
Meet the people behind the work.
Piumal leads your first conversation. Together, we bring product thinking, engineering and interface design to the brief.
The right problem
Piumal
Customer discovery, product requirements, learning design and client communication.
A solid foundation
Tharindu
Technical architecture, full-stack delivery and integrations.
A thoughtful experience
Yelka
Frontend development, interface design and usability.
A few useful answers
Costs, handover and next steps.
Different projects need different arrangements. We agree them before the work begins.
Is this only for education businesses?+
Learning and education are where our own product experience runs deepest. We also consider suitable websites, web applications and connected workflows for other service businesses. You do not need to use the ScienceDojo platform; engineering and learning design are separate offers.
Can you improve our existing application?+
Yes, we can discuss a defined React or Next.js feature, interface or workflow improvement. We review the relevant code, requirements and access arrangements before agreeing the work. For a tool connection, we check available settings, native integrations and platform restrictions first.
Can we start with one small piece of work?+
Yes. One website journey, application feature or integration is a useful starting point. We agree what is included, the inputs you provide and how we will check completion before development begins.
How do you estimate cost and timing?+
The estimate depends on the scope, existing code and content, required integrations, review work and acceptance checks. We clarify the important unknowns first, then agree fees, dates and the delivery team. Hosting, third-party subscriptions and continuing support are identified in the brief rather than assumed to be included.
What happens to the source, accounts and handover?+
We agree source access, usage rights, account ownership, third-party licences and setup or usage notes as part of the brief. The handover should make the agreed work understandable and maintainable. These arrangements are confirmed for your project before it begins.
What happens after delivery?+
We can discuss further features or a continuing development arrangement. Priorities, team availability, review cadence, maintenance and support responsibilities are agreed separately. A focused build does not automatically include ongoing hosting, monitoring or incident cover.
How will we know the work is ready?+
We agree completion checks for the actual journey: what users need to do, required screen sizes and browsers, relevant permissions and failure or recovery paths. You review working software against that brief. Any specialist testing or assurance your project needs must be identified and agreed in scope.
Do you provide general IT support?+
Our current focus is web software: websites, web applications and connected workflows. Computer repairs, office networks, a managed IT help desk and round-the-clock operational support are outside this offer.
05 / Start a conversation
Start with a conversation.
A few sentences about your current tools and the change you want will help Piumal understand the work.
Your first point of contact
PiumalDiscovery, requirements & client communication
Piumal reviews the brief and follows up by email.
We clarify fit, requirements and any access needed.
If the work fits, we agree scope, fees and dates before development.
