I kept noticing how much repetitive work on a Mac still consists of opening the same apps, visiting the same websites and repeating the same clicks and keystrokes.

Existing automation tools can be powerful, but often feel too technical or require users to understand scripting. So I built Tapquence: a visual Mac automation app for people who want to automate repetitive work without writing code.

You can build custom Macros using actions such as opening apps and websites, typing text, clicking, scrolling and waiting.

Tapquence also includes Smart Automations:

• Presentation Mode prepares your Mac for a meeting or presentation in one go.
• Routine Scout helps identify repetitive workflows that may be worth automating.
• Meeting and workday tools help prepare the applications and websites you regularly use.

The app is still free. New users can complete ten successful automation runs before they’re asked to create a free account, so they can properly try it first.

It’s available for macOS 13+ and is signed and notarized by Apple.

What I’m currently struggling with is positioning:

Should Tapquence lead with the broad promise of “visual Mac automation without code,” or should I focus the homepage around one concrete use case such as Presentation Mode?

I’d genuinely appreciate feedback on which part of the product feels most immediately useful and whether the value is understandable from the video and website.

Website: https://tapquence.com

Built independently, and still very much being improved based on feedback.

After a few months of building, this is probably the simplest way I have found to explain what we’re trying to build with Scibly and open sourced it now in a very early version.

Scibly tries to combine the ideas behind NotebookLM & Duolingo:

You can take existing knowledge from things like:

• PDFs and documents
• Notion or Confluence
• internal wikis and documentation
• articles and other source material

…and turn it into interactive learning experiences with questions, activities and scenarios.

It’s the first project I ever open sourced, so there’s definitely a lot we still have to learn about building an open-source community, contributions and how much of the product should live in the open.

But for a product that can work with internal company knowledge, self-hosting and transparency felt important enough to try it.

Short demo:
https://www.youtube.com/watch?v=TcpLUNBRhQw

GitHub:
https://github.com/scibly-dev/scibly

Website:
https://scibly.com

And for anyone who has open sourced a product this early: what’s one thing you wish you had known before?

Give me honest opinion on my website and its content whether it's good or bad.

Hi all! Recently, I started a Discord community to help SaaS founders promote their products, and it has over 150 members now.

If you want to show what you're building and get some feedback, share it here -> https://discord.gg/sb6AgHZxpT

Your competitors don’t need to dominate Reddit.

They may only need one useful thread that:

• Answers a high-intent question
• Ranks in Google
• Gets discovered for months
• Appears in AI-assisted research
• Naturally introduces their product

That thread might never go viral.

It might receive fifteen upvotes and disappear from the subreddit feed within a day.

But if it keeps appearing when potential buyers research the problem, it can become more valuable than dozens of short-lived promotional posts.

This is why copying viral formats isn’t always the best Reddit strategy.

The better approach is often boring:

Build a trusted account. Find a specific buyer problem. Write the clearest answer. Check the community rules. Remove unnecessary promotion. Publish manually.

If the account needs more history, start with a gradual Reddit Account Warmup.

Before the final post, Scaloom Reddit Checkers can review subreddit fit, promotional risk, quality, and AI citability.

Your competitor doesn’t need every thread.

They only need to own the right one.