Websites, CRMs and automations for your business. Built by a team of two.
What we do
Most clients come for a site and stay for what is behind it: the spreadsheets, the Monday report, the copy and paste between systems.
01Sites and web apps
Not a brochure. A site that books, sells, takes enquiries and tells you what happened, designed for your business rather than poured into a template.
02CRMs and client systems
A CRM shaped around how you actually sell, instead of a generic one you bend yourself around. Every lead, quote and follow up where the whole team can see it.
03Office automation
We find the tasks someone repeats every day and hand them to software. Reports build overnight, invoices send on time, and data moves between your tools on its own.
04Everyday tools
Not every problem needs a platform. Sometimes it is a dashboard, a bot or a fifty line script, and it saves somebody an hour every single day.
How we work
Every project travels the same seven stages. Here is what happens at each one, and what you have in your hands when it ends.
Stage 1 of 7
We start with how your business runs today, not with technology. Where time goes, what breaks, what you wish just happened.
Stage 2 of 7
We write down what is being built and what is not, what it costs and when it lands. Agreed in writing before anything is committed.
Stage 3 of 7
Screens, flows and the shape of the data. You see and click through it early, while changing it is still cheap.
Stage 4 of 7
The team that designed it writes it. Short cycles, a live preview you can open any day, and no handoff in the middle.
Stage 5 of 7
We wire it into the rest of your day: email, WhatsApp, payments, spreadsheets, the tools you already pay for. This is where the hours come back.
Stage 6 of 7
Security checked, tested on real phones, and shipped. We train your team and stay close for the first weeks of real use.
Stage 7 of 7
Software keeps moving after launch. We maintain it, fix what breaks, make the changes you ask for and add what you need as you grow.
Journal
The story of the studio and what we care about.
Before there were clients there were side projects: a game, a notes app, an attendance system and a Discord bot. This is how those turned into a studio.
Tidence began the way most good tools do, with people building things for themselves. Alexander Ross was designing interfaces and database schemas and pulling apart his own work to see where it broke. Bryan De Jesus was writing the backend systems that keep data moving between services. Separately, they kept shipping.
The projects were small but real. An arcade game with global leaderboards. A notes app with no ceremony. An attendance platform reporting in real time. A Discord bot handing out green points. A desktop app pulling live exchange rates. Each one was a lesson in finishing things, not just starting them.
Somewhere along the way the questions changed. Instead of asking how something was built, people started asking whether it could be built for them: a website that took bookings, a client list that lived somewhere other than a spreadsheet, a report that would just appear every Monday.
That was the moment Tidence stopped being two portfolios and became one studio. The name comes from the tide: steady, recurring work that keeps moving whether or not anyone is watching. It is how we think about software too. It should run quietly, every day, and keep running.
Built to be used, not shown.
Studio notes
We are not tied to one stack. Web and mobile, cloud and on-site, SQL and NoSQL, AI and the tools you already pay for: we choose what fits your problem and your team, and learn whatever the job needs.
Principles
Sell you a template as a custom build. Lock you out of your own code. Ship anything we have not tested on a real phone and checked for security first.
Write to us. We reply within one business day.
