OpenCNAM - How and Why We Built a Caller ID Name API

56badf521701d4f9b3a394d3ef6e90c4?s=47 Randall Degges
December 11, 2012

OpenCNAM - How and Why We Built a Caller ID Name API

This is a rather long talk (~40 minutes) which covers my full tech startup experiences while building OpenCNAM.

I talk about finding the idea, what the problem is, how OpenCNAM solves the problem, how we built the solution using Python and cloud services, and how we got customers and handled marketing.

56badf521701d4f9b3a394d3ef6e90c4?s=128

Randall Degges

December 11, 2012
Tweet

Transcript

  1. 14.
  2. 22.
  3. 26.
  4. 35.
  5. 36.

    What is OpenCNAM? A REST API for hackers that want

    Caller ID data without the bullshit.
  6. 40.

    $ curl -H "Accept: application/json" https://api.opencnam. com/v2/phone/+16502530000 { "updated": "2012-12-05T19:58:13.770770",

    "name": "GOOGLE INC", "created": "2012-10-12T06:53:05.194858", "price": 0, "uri": "/v2/phone/%2B16502530000", "number": "+16502530000" }
  7. 42.

    ... And Open ... • Free cached CNAM dips (60

    per hour). • No account necessary.
  8. 48.

    • Flask • Amazon DynamoDB • Heroku • Amazon Web

    Services • SSL • Service Oriented Architecture • PostgreSQL
  9. 49.
  10. 53.
  11. 64.
  12. 70.
  13. 75.
  14. 91.
  15. 94.
  16. 95.

    Google your industry. Find your customers. Put contact names, company

    URLs, and emails into a Google doc. Email 3 customers per day, asking for feedback. Listen to feedback.
  17. 100.