aytekin

We built a ChatGPT app that lets you create and manage Jotform forms through conversation. You can generate forms, refine them, and analyze submissions without leaving ChatGPT.

Here’s the link: https://www.jotform.com/chatgpt/

Happy to hear feedback or questions.

@aytekin

Since we know that 3 out of 10 users who receive this offer will accept it we segment users by industry / feature usage etc. and send offers to talk to them to listen their stories and feedback.

I think the unstated “first version” part is important. You should be gradually adding the missing parts. And not just leave it at the great, simple but missing too many things state forever.

Writing is a public act. You might still be expecting some readership without the expectation of ad money or promotion of something.

What I miss most about the blogs in 90s and early 00s is the conversation between blogs by linking, quoting and commenting each other. Reading blogs involved going from one blog to another, and reading blogs of 10 people about a single issue. It was a conversation. And you would constantly discover new blogs this way.

“Do you take credit or debit cards?

No, GoCardless is an ACH debit company.”

Most people prefer credit cards. How does it work? Do you ask people if they want to pay by ACH?

Or do you detect debit cards on your credit card form and use this instead of the credit card processor?

How? User testing, full story, user interviews, detailed product metrics, continuous improvements and giving your designers a lot of power.

We had to hire 3 sales people before we found someone right. It is like someone hiring developers without any development experience. You get it wrong because you don't know what makes someone good. Get help from someone who has experience. We finally found the right person from our network and suddenly sales started flying.

Since their APIs covers everything this should be possible. Be the first UXaaS.

A killer feature: a server by server breakdown of Google Cloud expenses. It is impossible to understand what you are paying for on Google Cloud. They lump everything together in an incredibly confusing bill.

The title should have been "How we send 22000 emails every hour for $9/month"

16 million emails for $9 is actually pretty good.

If the work has to be done individually, then there is no point in being co-located. Remote works well.

Co-located teams communicate well, decide and move quickly, and has much higher trust between team members.

Work that does not require too much communication, speed and collaboration is more suitable to remote.

This hybrid approach worked well for us.

Knowing only you have access to tha data is a good thing. For example, we are able to host our internal employee feedbacks and reviews on our own forms without worrying about a sysadmin or database admin having access to it.

I understand the concerns about client side manipulation but that is hard to do without leaving a trail on our code commit history. Both system and product changes can only be done by code commits.

You cannot protect systems with a single perfect security solution. You have to be paranoid and have many layers in your security model. This may not be the silver bullet, but this greatly enhances the security.

By the way, here are the tricks I do to do inbox zero on gmail: https://www.entrepreneur.com/article/290175

https://searchengineland.com/4-of-the-google-index-hit-by-de...

They only make sense if you are small in scale. Use them when you are starting out and then build your own after you have a good number of paid users.

Ahrefs recently announced a similar growth rate: https://medium.com/swlh/how-we-achieve-65-yoy-growth-by-igno...

An amazing book full of great stories and lessons to learn from people who made incredible innovations like the first iPhone. My favorite parts are the story of the iPhone keyboard and detailed encounters of Steve Jobs demos he has given.