Ethos & Principles

💡 Our Ethos

❤️ Love

At Symph, our work is fueled by love and passion. We love to build products that people love to use. We put a lot of skill and effort into what we do because we want to be able to create things that people would value.

🦋 Change

We desire to help change the world positively, and help people with the same vision, act on the same. Similarly, we strive to help Symph (as a company) and ourselves change for the better as we believe that change is the key to growth.

💻 Hack

We always find ways to turn the No’s into Yes’s. We do what we can to turn the most “ambitious” ideas into concrete products, to turn the impossible into something that can actually be done. “Challenge Accepted” is the statement we live by.

Strategic Anchors

FASTEST IN THE MARKET

end to end startup fast (validate, build, launch, iterate, learn)

REVENUE-FIRST

revenue from day one

no burn cash first strategy

BUILDING IN THE OPEN

solve real problems transparently

thought leadership

no isolated building

ALL STARTUPS ALIGNS TO AN SDG GOAL

🧠 Our Principles

🐥What makes Symph different?

We are people who understand business and the role that tech plays in it.

Example: Instead of saying “Your business needs XYZ so you should get XYZ.”, we approach it as: “Your business needs XYZ but considering your targets and constraints this year, we can help you do ABC. The pros and cons of the other are….”

🧭What are our guiding beliefs?

Technology is the tool that must adapt to business needs.

Technology design is a means to do good business.

Design thrives within constraints.

Assume positive intent.

We exist to help others use technology to enrich their businesses.

Note: Take in all this information with the knowledge that this is a single step towards the dream to make Symph a successful Startup Builder (Not just a fancy product but an innovative and thriving business.). Think of it as “Symph births and grows many startup businesses.”

🤝Work & Collaboration Principles

Use realistic data when sending mockups or the test site to our clients so they can observe a realistic experience.

Deliver value early and often to a client.

When you have a single person assigned to an area or task, then you are reliant on that person and could lose productivity or get stuck when that person is unavailable or leaves.

Read error messages properly. They are usually useful. The inverse is true. When writing error messages, make them accurate and useful.

People are able to focus better when they are working on one task or project at a time.

More often than not, deploying something right before a demo causes a lot more headaches.

Sync internally first before syncing externally.

Leaders set the vision. Frontliners think of the details. Leaders ask questions and give feedback.

When doing something, create a quick video to document what you did, so that knowledge is shared without a meeting to explain it.

Use Loom⁠

⁠

All members of a team working on a project should be involved in talking and communicating with all the stakeholders of the project - including the client and its end users.

The book "Principles" by Ray Dalio is a highly recommended reading! At the very least, you can start with the following PDF summary.

⁠

This is a summary of the book Principles by Ray Dalio.

⁠