Ask HN: Any interest in learning how startups actually work?

I am <i>incredibly</i> interested in well-documented business or technical processes, particularly at startups that run at a smaller scale than the Google / Facebook / etc tier who usually publish that sort of thing.<p>What's interesting? Oh, where to start, where to start. Dashboards. Metrics. Customer service processes. Architectural decisions. Rationales and priorities, most particularly "We intentionally avoid doing X, because..."

Very interesting. I'm interested in hearing about working with open source projects, selling data, and customer support; I'm especially interested in how startups handle bugs in newer open source projects. Do you spend time identifying the cause and submitting a patch, switch technologies, or work on something else and punt the decision?<p>This is a specific system design question, but I'd also like to hear about choosing between job queues (e.g., Beanstalk) and batch systems (e.g., Hadoop) for soft real-time data processing.<p>Interesting startups to interview:<p>- FlightCaster and BackType (lots of data, users get product for free, discuss process of finding and selling to customers interested in associated data; both also deal with real-time data)<p>- Shopify (supporting users that use your product to sell their product)<p>- banksimple (regulated industry)<p>- DuckDuckGo (building a system to compete with a wealthy behemoth)<p>- WakeMate and Square (designing and manufacturing hardware)

Clickable: <a href="http://www.resultsjunkies.com/blog/back-office-exposed-zippykid/" rel="nofollow">http://www.resultsjunkies.com/blog/back-office-exposed-zippy...</a>

I'd be interested to see how processes work at a bootstrapped vs. funded start up. A comparison table would be awesome!

Yes this is useful. In terms of the "infrastructure" I would drill deeper around surprises for people, what pieces they see as critical, etc.; just knowing the infrastructure is much less valuable than its relative importance and key lessons around its use... Good luck

Awesome, but way too short. To be really interesting, make it 5 times longer and more detailed.

As an engineer I want to request you to devote more questions to the infrastructure and the architecture in place. I would want to know the big architecture picture, alternatives that they researched, why they chose certain technologies , the human resource devoted to delivering the technical product, the ratio of technical-nontechnical in a team etc. Thank you for the initiative.

Hey Guys, I'm Vid Luther, the founder of Zippy Kid, any engineers etc that have any specific questions/comments I'll try to answer them here.

I'm definitely interested in this idea. I was really impressed with your Mixergy interview, so I have high hopes for something like this.

Maybe you can share some approaches which didn't work? And, of course, their working replacements.

Sort of like a startup postmortem without necessarily the mortem part? I like it! Would be good specifically for those of use just venturing in to Startup Land :)

Probing for as much 'open-ness' as possible is the #1 thing I'd like to see. Things like 'share your financial model spreadsheet' and other documents like this would be essential. I'm doing something similar with salon owners at the moment as I'm launching a small salon software kit in the next few weeks.<p>Will definitely check back every once in a while!

I like it.<p>The only thing I'd say is, get interesting startups -- and the rest will take care of itself.