Business control and compensation

[phppup]

I was asked to create a form and database system for a local entrepreneur and need some business advice and acceptable practices input.

From the technical side, I'm concerned about keeping my intellectual property secure and private. If I allow the 'customer' to have access to the files I create, I may not be needed long term.
How can I maintain control over the code that I write? And the database that it populates?

From a business standpoint, are there generally accepted guidelines for ownership of intellectual property?

I also have questions regarding compensation.  Is there a ballpark of generality based on hours invested or (USA) dollars for such an endeavor or it's pieces?

[gizmola]

12 hours ago, phppup said:

I was asked to create a form and database system for a local entrepreneur and need some business advice and acceptable practices input.

From the technical side, I'm concerned about keeping my intellectual property secure and private. If I allow the 'customer' to have access to the files I create, I may not be needed long term.
How can I maintain control over the code that I write? And the database that it populates?

From a business standpoint, are there generally accepted guidelines for ownership of intellectual property?

I also have questions regarding compensation.  Is there a ballpark of generality based on hours invested or (USA) dollars for such an endeavor or it's pieces?

If you're developing code for someone at a cost, typically they would expect to own that code or a license to that code in return for the payment they are making to you.  

Generally speaking, the "data" for a system is the property of the customer/business using your system.  

It's not unusual for companies to provide a separate "maintenance" agreement that covers a period of time, wherein the customer would pay you an amount to enhance it and fix bugs.  You also could provide the system in a Software as a Service model, where you host the system and code, and provide the customer access to the application, without otherwise providing the system level access they would need to even see the code.

As far as pricing, there are many ways to estimate and cost projects.  Understandably companies tend to like to know a price for something, so you need to have a decent idea of what amount of time it will take you to build the features.  You make this estimation in "ideal" time, which is the amount of time any feature might take if you are head-down and fully productive.  Then add a reasonable amount of overhead to your ideal estimate (anywhere from 10-35% is not uncommon).  Determine a reasonable market rate for your time, and in combination, you'll have a "by feature" estimate you can utilize as a fix bid, with associated milestones.  

Any project like this should involve a contract.

[phppup]

@gizmola it would seem that the Software as a Service model would be more in line with my thinking (since I fear my code being co-opted). How is this best implemented?

In simple terms, if the customer wants users to complete a form, would I just re-direct them to a form on MY server? Wouldn't that seem a bit suspicious if detected?

[gizmola]

2 hours ago, phppup said:

@gizmola it would seem that the Software as a Service model would be more in line with my thinking (since I fear my code being co-opted). How is this best implemented?

In simple terms, if the customer wants users to complete a form, would I just re-direct them to a form on MY server? Wouldn't that seem a bit suspicious if detected?

I don't really want to guess at what the application is, but SaaS would entail you hosting the application on your infrastructure and the customer using the functionality you provide within the app as an end user.   There's no subterfuge involved in it.  If there's some reason that a user would believe they were tricked in some way, then it's not SaaS.

[phppup]

@gizmola As stated, just starting with a simple form to register users and collect information (eg: name, address, email, phone) for an easy access point that might be used later for sales' campaigns.

I guess the real question is: How do I optimize my earrings and ensure that I don't have my work ripped-off by unscrupulous sources?

[gizmola]

6 minutes ago, phppup said:

@gizmola As stated, just starting with a simple form to register users and collect information (eg: name, address, email, phone) for an easy access point that might be used later for sales' campaigns.

I guess the real question is: How do I optimize my earrings and ensure that I don't have my work ripped-off by unscrupulous sources?

If the form is a "web form" then host it, and store the data within your own infrastructure, and you've accomplished SaaS, with all the benefits of code ownership we've discussed.  You do need to account for the fact that you'll be paying for hosting.  There are many solid/reputable hosting companies that provide a virtual server with room to grow your application, where you'll know your price in advance.  You also want the server to be in a DC that is co-located near to your customer, and these mid size hosting companies tend to have that type of coverage.

Linode, Vultr, Hetzner and Contabo  are a few of the better known companies with track records to compare and contrast.  I would highly advise against using shared hosting.  Given that you will be running a monolithic architecture, I'd suggest looking at 8gb vps's to give you room to run the mysql database as well as your webserver/php stack.

[phppup]

@gizmola I appreciate all your help.

Now I think we've come full circle and returned to my initial conundrum.  If the business already has a minimal web presence with a registered domain, how can I incorporate MY form without making ripples in the pond.

If I host it myself, then users are being re-directed. And if I put my code on the business domain server, then I no longer have exclusive access to it.

What is the best solution for me?

[gizmola]

I really have no context with which to give you a "best solution" but a longstanding way of handling this is to have the customer website utilize an iframe that wraps your hosted site.